Version 6.1 adds the ability to manage AWS tags on your servers by linking them to CloudBolt server attributes. When the value of the CloudBolt attribute changes on the server, so will the value of the tag.

How to Use Tags

One potential use case is to manage your AWS cost center tags. Say you want servers provisioned by your Dev group to have the Cost Center tag set to 1. Here are the steps to make that happen:

  1. Create a new Cost Center parameter in the Admin interface. Make sure to select “Show on servers” to make the parameter taggable, and select “Required” if you want to hide it on the order form.
  2. Add the parameter to the Dev group, and add 1 as the sole option.
  3. Under the Tags tab of the resource handler, add a new tag, Enter Cost Center as the Tag Name, and select cost_center as the attribute.

Now whenever the Dev group provisions a server, the Cost Center parameter and tag will both be set to 1.

Bidirectional Syncing

Tags are created on the server at provision time, but they can also be updated on servers anytime. If you edit a parameter on a server in CloudBolt, it will automatically write the new value to the linked tag.

Likewise, changes to tags in AWS can be detected by CloudBolt. When you run the Refresh Info server action on a server, CloudBolt will not only update the “Tags” section of the server, but also the “Parameters” section for any parameters that are linked to tags.


Syncing from AWS tags is only supported for Parameters, not built-in server attributes like owner, environment, or group.

Unlinking Tags

If at any time you decide that you no longer want to link a tag to a parameter, you can simply delete the link from the Tags tab of the resource handler. Existing servers will still have the tag set on them, but changing the parameter value will no longer update the tag value.