We need tag synchronization between AWS and MIQ! Here are the details on why and how we leverage tagging in AWS.
Tagging resources in AWS is not optional. Each team is responsible for tagging their resources, whether it is a short term (ephemeral) environment for testing, or a long standing (static, non-ephemeral) environment.
At the very least it allows us locate the team or individual responsible for a particular resource in AWS.
It also allows the consolidated bill to be reconciled against the projects as well as provide administrative access.
Tags enable you to categorize your AWS resources in different ways, for example, by purpose, owner, or environment. There are some set tags that AWS provides like stack name.
Each custom tag consists of a key and a value, both of which you define. For example, you could define a set of tags for your account’s Amazon EC2 instances that helps you track each instance’s owner and stack level.
Projects are expected to Tag every single resource inside of the AWS account and risk the resource being removed if the appropriate tags are not implemented.
The tags that are required are:
Project – Name of the project
Environment – Dev, QA. PProd, Prod, DR
Component - REST, web, scaler, worker - a deployable chunk of a project/system - could deploy a fix to one without having to redeploy the other pieces
Version - Deployed version
OwnerEmail - the email address of owner of the deploying resources.
Tags should be applied programmatically so to prevent any untagged resources entering AWS and also to provide a consistency in the use of them.