[tvlk-dev] Tag your resources in AWS

As we are moving aggressively towards optimising the infrastructure cost, It has become very important to tag all your resources as per the guidelines by Site-infra.
We scanned our tvlk-dev account and found 14,183 non tagged resources. This may be a problem as we will not be able to monitor the cost for these resources.
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

Which resources are affected ?

Check the sheet which contains all the details here, If any resource which you are using is mentioned in the sheet, Then please follow Site-infra guidelines to tag your resources .

Tags which are invalid

We have also observed that many of the resources and tagged but they are not following the conventions as mentioned here, Please make a note productdomain Productdomain productDomain are invalid tags and also need to be fixed. Please tag your resources as per SI guidelines.

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"
}

Apply the changes

#2: You provisioned the resources via AWS console/CLI

#2.1:

#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.

References

[1] https://docs.google.com/spreadsheets/d/1ThrHlOjk7OfUOBuADn-9Cw0nB8pxCN8boVPpSBDQ1rA/edit?usp=sharing
[2] https://29022131.atlassian.net/wiki/spaces/SI/pages/196952337/AWS+Resource+Tagging+Policy
[3] https://tvlk.slack.com/files/T02T3CAFM/F011X5DHQTA?origin_team=T02T3CAFM