[psa] Tag Your AWS Resources on tvlk-dev Account
TL;DR:
- Tag your AWS resources on
tvlk-dev account for cost-attribution.
- Follow Cloud Infra's AWS Resource Tagging Policy. In this case,
ProductDomain tag is the most important.
- Deadline: Friday, 17th of April 2020 - 12.00 pm (UTC+7).
- We will decommission untagged resources without confirmation after deadline had passed.
Why?
In the spirit of cost-reduction effort, cost-attribution is required to increase visibility and accountability. On a shared account environment such as tvlk-dev, proper cost-attribution can be achieved by proper resource tagging. As of now, almost half of the total cost of tvlk-dev comes from untagged resources. This cost cannot be attributed to a specific ProductDomain/BU.
Which Resources must be Tagged
- All resources which you want to keep, otherwise you can just decommission them.
- All resources which supports tags must be tagged. Some of the top resources:
- EC2 (ASG or instances)
- ELB
- RDS
- ElastiCache
- Elasticsearch
- CloudWatch
- CodeBuild
- ECS
- DynamoDB
- Lambda
- S3
- SQS
How to Find Untagged Resources
#1:
- You can use Tag Editor to find untagged resources (there are some unsupported resources).
#2:
- Open each resource page.
- Filter by closest name which you can think of.
- Check if tags exist manually.
How to Tag AWS Resources
#1: You provisioned the resources via Terraform
- Add
tags in your Terraform code, for example:
tags = {
Name = "${module.launch_template_name.name}"
Service = "${var.service_name}"
ProductDomain = "${var.product_domain}"
Environment = "${var.environment}"
ManagedBy = "terraform"
}
#2: You provisioned the resources via AWS console/CLI
#2.1:
- Login to AWS Console and tag your resources manually.
#2.2:
- Use Tag Editor (there are some unsupported resources).
#2.3:
- Use AWS CLI for resources which are not supported via AWS Console and Tag Editor.