AWS Cloud Operations Blog

Introducing Tagging Support for AWS OpsWorks Stacks

AWS now supports tagging of AWS OpsWorks Stacks application environments. Tags that you add to a stack and layer now automatically propagate down to all underlying AWS resources, including Amazon EC2 instances, Elastic Load Balancing load balancers, Amazon RDS databases, Amazon EBS volumes, and Amazon ECS clusters. This benefits everyone who wants to track their AWS usage for OpsWorks Stacks infrastructure and components.

OpsWorks Stacks is a powerful AWS configuration management service that lets you model applications, ensure uniform configuration across groups of resources, and scale fleets of instances. Tags are key-value pairs that you can link to AWS resources for business, technical, and other purposes.

Until now, customers who wanted to track the costs of their OpsWorks applications or components had to tag all underlying resources manually. Now, you can simply add tags to your existing stacks. The great thing is that tags work similar to custom attributes in OpsWorks Stacks. Tags that you specify on the stack are automatically inherited by every layer in that stack, where you can override values and add extra layer-specific tags.

OpsWorks does the heavy lifting of computing a resulting tag set and applying it to all the linked resources. Additionally, OpsWorks ensures that new resources that you create in a layer or assign to the layer are tagged automatically. OpsWorks gives you the ability to add, update, or remove tags on stacks and layer at any time, and then update tags on your AWS resources accordingly.

For more information on how to apply tags to your stacks, see the documentation.