Most AWS services support the tagging of resources. You can use tags to apply arbitrary metadata to AWS resources. This metadata is available with the resources, and can be used for a variety of purposes. Here are some examples of what you can use tags for:

  • Generating cost-utilization reports.
  • Providing information about teams developing the product such as contact information.
  • Specifying which resources may be automatically shut down or terminated by an external script.

Handel Support for Tagging

On resources that support it, Handel allows you to specify tags for that resource. It will make the appropriate calls on your behalf to tag the resources it creates with whatever tags you choose to apply.

AWS services have limits on the total number of tags that may be applied to each service. Generally that limit is currently 50 tags.

See a service such as EFS (Elastic File System) for an example about how you can apply tags to Handel services.

Default Tags

In addition to the ones you specify yourself, Handel will automatically apply the following tags to your AWS resources:

  • app - This will contain the value from the name field in your Handel file, which is the name of your overall application.
  • env - This will contain the value of the <environment_name> that your service is a part of.

See Handel File Explanation for a refresher on where these automatically applied values fit in your Handel file.