A CLI tool that automatically creates and maintains tags across AWS, Azure, and GCP resources in Terraform/OpenTofu infrastructure.
Terratag is a CLI tool that automatically applies and maintains consistent tags or labels across AWS, Azure, and GCP resources within Terraform or OpenTofu infrastructure code. It solves the problem of manual, error-prone tagging by integrating tag management directly into the Infrastructure as Code workflow, ensuring governance and enabling cost tracking.
DevOps engineers, cloud infrastructure teams, and platform engineers who manage multi-cloud environments using Terraform or OpenTofu and need consistent resource tagging for cost management, security, and operational visibility.
Developers choose Terratag because it automates a tedious but critical aspect of cloud management, works across all major cloud providers, integrates seamlessly with existing Terraform/OpenTofu workflows, and provides fine-grained control over how tags are applied without modifying original infrastructure code.
Terratag is a CLI tool that enables users of Terraform to automatically create and maintain tags across their entire set of AWS, Azure, and GCP resources
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Applies tags consistently across AWS, GCP, and Azure resources, as evidenced by the supported provider list (aws, google, azurerm, azurestack, azapi), solving a key multi-cloud management pain point.
Creates new .terratag.tf files and preserves originals as .bak backups by default, ensuring safe operation and easy rollback without modifying source code.
Offers filtering with regular expressions and tag merging controls (e.g., --keep-existing-tags), allowing precise targeting and management of tag application.
Compatible with Terraform 0.12 through 1.x and OpenTofu 1.x, as stated in prerequisites, making it suitable for legacy and modern IaC setups.
Only supports AWS, GCP, and Azure providers; missing other clouds or custom resources, which restricts use in heterogeneous environments.
Generates additional .terratag.tf and .bak files that can clutter directories and complicate version control, especially with repeated runs.
Requires running terraform init or tofu init first, adding an extra step and potential point of failure before tagging can occur.
New tags override existing ones by default, which could unintentionally remove important tags if the --keep-existing-tags flag is overlooked.