How to tag on AWS
Use Cases:
Automation
- Use tags within scripts to tell hordes of resources to do things
- Versioning of resources to archive, update, or delete
- Turn off dev environments during non-business hours to reduce costs
- Tag instances that touch sensitive or confidential data to pass security audits
Operations Support
- Use tags from systems that trigger monitoring systems to attach to tickets
Tagging
Syntax
- Typically all lowercase
- Hyphens
(-)separating words- Example: dev-nginx-ec2
Consistency
- Turning off dev environments during non-business hours use case: use a single tag across all instances and teams / departments for easy automation.
Cost Allocation Tags
- Only starts capturing cost data from the time you initiate new tag
- If you change a tag on an existing resource, it will only have the data related to the new changed tag. All past data will not apply to new tag.
Things to note
- Tags are free
- Tags are case sensitive
- Tags limited to 50 per resource