Surprised by your Cloud Bill every month? Try Cross-Cloud Tagging


If you have recently received the bill from your cloud provider, you may be still wondering how you spent all this significant amount of money in cloud resources. And if you’re using multiple cloud providers (like we do at ElasticBox), this problem is even more complicated. Evidently, you need to have much better insight into where your expenses are going. Resource tagging is a crucial technique to improve the cost efficiency and reduce your infrastructure bill.

Without tags, you won’t be able to confidently know what each of your instances is doing, which instances have been provisioned and which you can power off. This technique is even more important when using autoscaling systems that automatically add and release resources based on the workload of your application.

Tagging your cloud resources allows you to add metadata to your resources in the form of key-value pairs. Hence your tag-key must be a meaningful value that represents how you want to report this resource, while the tag-value should give you an insight of what you want to report on. These tag-keys will appear as columns in the reports of your cloud providers. Therefore they may be descriptive enough to help you to break down your expenses in the cost reports of your cloud providers.

In ElasticBox, we help you to manage the resources of your organization by offering a tagging system across cloud providers. This system allows you to add tags at the organizational level to control all the resources used in your organization, independently of your cloud provider. Nowadays, we support the definition of tags in resources of diverse cloud providers like AWS, GCE, VMware vSphere, HP Cloud, as well as all these providers whose infrastructures are based on Cloudstack and Openstack.


To add metadata to your resources, you just simply need to go to the Admin Console, in the Providers menu you have to click on Tags tab, and then you will be able to start adding tags to your resources.


To facilitate the tagging definition to our users, we settle a predefined list of 10 tag values, in the following named as “Preset”, which are meaningful for your organization and logically group the parts of your application and business. Additionally to this list, we also allow users to define their own key-value pairs with custom values.

  • Custom: Enter any value that’s meaningful to categorize resources, like department name.
  • Preset: Choose from preset values such as box name, environment, and so on. Preset values give specific information about a resource. Choose a value from this table.

Preset Value


Box name

Name of the box deployed.


Environment name the user gave in the deployment profile when deploying the instance.

Instance ID

ID assigned by ElasticBox, for example, i-extwmf.

Provider name

Provider defined in ElasticBox to which the instance was deployed.

Service instance ID

Unique ID for every machine created for the instance, for example eb-ek73d-1, eb-ek73d-2.

Service ID

ID for the type of service deployed from the provider, for example eb-ek73d.

User email

Email of the user who deployed the instance.

User ID

A unique ID to identify the ElasticBox user.

Workspace ID

Unique workspace ID where the instance was deployed.

Workspace name

Name of the workspace the instance was deployed from.


With this feature, we believe organizations will be able to better manage how their resources are being utilized, and consequently reduce their infrastructure bills. To learn more about how to define tags for your cloud resources, please visit our documentation. For a demo about how this tagging system can benefit your particular use-case, please contact us.

Hacker News

Categories: AWS, Cloud Application Management, Cloud Computing, Cool Features & Tutorials, ElasticBox, Google Cloud