Propagating Tags from provider level down to all resources using Terraform Template

Inheriting Tags from Top-to-Bottom

Resource Tagging is one of the most important steps in knowing your assets in the public cloud. With proper tag, you know the resource purpose, ownership, environment, data classification, regulatory compliance requirement, cost center, and many other attributes. This allows you to know your risk based on the data sensitivity, define security controls to protect assets, and allow for cost-benefit analysis.

Identifying the public cloud resources and ownership is the first step in satisfying asset management.

Organizations are using Terraform to manage their Infrastructure as a code (IaaC). Meaning the whole cloud infrastructure can be defined in the Terraform template (i.e., ec2 instance, type, what image, EBSvolume, encryption, subnet, elastic IP address, etc, etc). Terraform plan command lets you see all the new additions, removal, and modification to the infrastructure before applying them. Terraform lets you define resources within config files such as variables, resources, and modules. Overall, it's the best-in-class tool that allows infrastructure to be built, modified, and to track changes with ease.