AWS OpsWorks Stacks Adds Custom Tagging Support
AWS OpsWorks Stacks now supports custom tagging for AWS resources, improving the ability to organize your resources and report on AWS cost allocation. Previously, you had to manually add and maintain custom tags on all OpsWorks managed resources. Now you can leverage OpsWorks for tag management. After you apply tags to a stack or layer, OpsWorks propagates the tags down to Amazon EC2, Elastic Load Balancing, Amazon RDS, and Amazon Elastic Block Store resources. This makes it easy to break down costs on an environment, application, or software component level. You can apply tags through the OpsWorks console, the CLI, SDK, or API.
AWS OpsWorks Stacks now supports custom tagging for AWS resources, improving the ability to organize your resources and report on AWS cost allocation. Previously, you had to manually add and maintain custom tags on all OpsWorks managed resources. Now you can leverage OpsWorks for tag management. After you apply tags to a stack or layer, OpsWorks propagates the tags down to Amazon EC2, Elastic Load Balancing, Amazon RDS, and Amazon Elastic Block Store resources. This makes it easy to break down costs on an environment, application, or software component level. You can apply tags through the OpsWorks console, the CLI, SDK, or API.
AWS OpsWorks Stacks custom tagging is available in US East (N. Virginia), US East (Ohio), US West (Oregon), US West (N. California), South America (São Paulo), EU (Ireland), EU (Frankfurt), EU (London), Asia Pacific (Singapore), Asia Pacific (Tokyo), Asia Pacific (Sydney), Asia Pacific (Seoul), and Asia Pacific (Mumbai) public AWS regions.
To learn more about tagging in AWS OpsWorks Stacks, visit our documentation or product page.