...
- "Technical Contact"
- This should be a netid
- "Functional Contact"
- This should be a netid
- "Environment"
- dev
- test
- stage
- prod
- dev/test (for cases of where a resource is shared by multiple environments, e.g an RDS DB hosting both dev and test schemas)
- "Application"
- Identifies the software application this Amazon resource supports.
- Resources used by multiple applications could have a suggested value of “infrastructure”
- the application should be in all lowercase
- This tag is required on all billable resources for CIT AWS accounts
- For resources used by staff for learning, experimentation, and trials, we suggest using the value of "sandbox".
- In the joint training account, we suggest using the value "training".
AWS resource types that cost money but cannot be tagged
Note that not all AWS resource types that cost money can be tagged. Here are those resource types:
- CloudTrail
- Config
- CloudWatch (alarms, log streams, etc)
- Lambda
- API Gateway
- SES
- SNS
- SQS
- Directory Service
- AppStream 2.0
- Lightsail
Note: The above list may not be exhaustive!
How to determine what's tagged and what's not
- Use the resource tag editor in your AWS Console: https://resources.console.aws.amazon.com/r/tags
- The following resource types can be tagged but cannot be accessed via the above AWS tag editor:
- WorkSpaces
- CloudFront
- EFS
- DynamoDB
- The following resource types can be tagged but cannot be accessed via the above AWS tag editor:
- In CloudCheckr: http://support.cloudcheckr.com/tagged-untagged-resource-reporting/
...