Using Resource Level Tags

We recommend defining your environments at the organizational unit or account level. It makes analysis and maintenance of application environments simpler. If you need finer control over environment definition, it is possible to define it at the resource level.

It is possible to define an application's environment at the resource level by tagging these Compute resource types:

• Application Scaling Group

• Container

• Function

• Instance

For example, you have an application using AWS Elastic Container Service and it is an account that is tagged with the environment Development. Here are two views of that application deployment showing its inherited environment Development:

First, update the Environment Tag Development to allow it to be overridden.

Then add an Environment tag to your container service resource in its account, e.g., in AWS add Environment:Sandbox.

Then confirm that resource tag is harvested in Heeler

Then confirm that application deployment Environment has updated: