Tags provide specific identification and classification of AWS resources by associating them with descriptive metadata. A tag basically consists of a key and a value, both of which are defined by the user. Once defines, these tags can be used to filter when requesting specific resources.

What is AWS Naming Convention?

By using tags, you can add metadata in the form of tags to AWS resources. Each tag is a straightforward label made up of a user-defined key and an optional value that helps simplify managing, finding, and filtering resources.

By applying business and organizational information to your utilization and costs using tags on AWS resources, you can gain extra organizational-specific insights into optimization.

You can write general-purpose automation scripts based on tags rather than specific resources by tagging AWS resources.

What tags should I use on AWS?

Establish guidelines for their use as you decide the AWS tags you need and how you’ll use them. Select the AWS tags that must be used, the delimiter that must be used, and the person in charge of producing them. If you have a lot of resources already, you might need to assign tags to the teams that use them.

Engineers can find and use resources more easily with the aid of technical tags. These could be an environment, a version number, the name of an application or service, etc.

Stakeholders can monitor costs and the teams or business units in charge of each resource thanks to business tags. To calculate the return on investment of the endeavor, you might want to know, for instance, what proportion of your AWS spending is going toward the new product you released last year.

Security Tags make guarantee that security and compliance requirements are met throughout the firm. These tags may be utilized to restrict access or to indicate certain data security requirements for HIPAA or SOC compliance.

The cleanup, shutdown, or usage rules for any resource in your account can be automated using automation tags. For instance, after sandbox servers are no longer in use, you may tag them and run a script to destroy them.

What are the main advantages of using tags to label AWS EC2 instances?

Using a consistent tagging method can make it simpler to manage your AWS infrastructure, monitor cost and consumption, and filter and search for resources. This article expands on the best practices and recommendations given in the whitepaper Organizing Your AWS Environment Using Multiple Accounts.

You may use tags to organize your AWS resources in a variety of ways, such as by owner, environment, or purpose. This is helpful if you have a lot of resources of the same type because you can easily recognize a particular resource based on the tags you’ve given it.

Tagging Restrictions

Maximum number of tags per resource – 10

Maximum key length – 127 Unicode characters 

Maximum value length – 255 Unicode characters

Tag keys and values are case sensitive 

Tag keys must be unique per resource  

Do not use the “aws:” prefix in your tag name or values because it is reserved for AWS use

They also tackle on other topics such as tagging API and CLI Commands and Tagging Filters using AWS Tools for Windows PowerShell.


Tagging is an effective tool to help manage AWS resources at increasing scale, providing the ability to identify, classify and locate resources for management and billing purposes.


Amazon EC2 filtering provides a way to both locate tagged resources and validate that the tagging standards in your organisation are being properly implemented. Naming best practices can be leveraged to achieve consistency across your environment and maximise the benefits that tagging has to offer.

If you would like to learn more. Kindly contact us now!