Best Practices for Terraform AWS Tags
summary
Introduces Terraform's default_tags (Terraform 0.12.31 + AWS provider 3.38.0) as a 10-line way to auto-tag almost every AWS resource, shows using data.aws_default_tags to read keys, and demonstrates concrete workarounds: create alternate provider for S3 objects (10-tag limit), remove duplicate tags to avoid the exactly identical tags error and the partial-match plan churn, use propagate_at_launch for ASG tags and tag_specifications/merge for launch templates and EC2 volume tags so attached volumes inherit tags.
AI-written summary · about
chapters (6)
- 0:00Introduction to AWS tags
- 2:32Why use Terraform default tags
- 8:20Setting up default tags
- 15:09Common bugs with default tags
- 20:47Workarounds for ASGs and volumes
- 27:57Key takeaways and Q&A
related talks
29mTerraform Practices - The Good, the Bad, and the Ugly
39mTerraform Practices to Enable Infrastructure Scaling
24mThe Power of AWS Tags
15mTerraform AWS Cloud Control Provider – Under the Hood
55mTerraform-ing your Cloud
29mManage AWS Resources With Terraform & AWS Cloud Control API
28mDynamic AWS Security Groups with Terraform
21mI Can’t Do This With Terraform, Now What?