The Terraform AWS provider serves as the bridge between Terraform configurations and AWS, enabling users to define and manage AWS resources as code. We are excited to share that version 6.0 of the Terraform AWS provider is now generally available. Along with bugfixes, the latest update brings enhanced multi-region support and other workflow improvements.<\/p>\n
With this release, AWS and HashiCorp continue to expand their partnership \u2014 delivering new integrations that help customers move faster, adopt more AWS services and features, and deploy infrastructure with developer-friendly workflows.<\/p>\n
Previously in the Terraform AWS provider, each provider configuration targeted a single AWS region. With this limitation, practitioners had to update every configuration file individually if they wanted to change a particular resource\u2019s configuration. For global companies, this could mean editing the same parameter in up to 32 separate configuration files for each region.<\/p>\n
With 6.0, the AWS provider now supports multiple regions all within a single configuration file. This new approach leverages an injected region attribute at the resource level to simplify configuration efforts. This method also reduces the need to load multiple instances of the AWS provider, lowering memory usage overall.<\/p>\n
Here are some more key highlights in this feature:<\/p>\n
Single provider configuration<\/strong>: Reduces the need to load multiple instances of the AWS provider, lowering memory usage. This example shows how to use the new region attribute for the awsvpc<\/em>peeringconnection<\/em>accepter in your Terraform configuration: <\/p>\n provider “aws” { resource “aws_vpc” “main” { resource “aws_vpc” “peer” { cidr_block = “10.1.0.0\/16” # Requester’s side of the connection. # Accepter’s side of the connection. vpc_peering_connection_id = aws_vpc_peering_connection.main.id This is an example of how to use the new region attribute for the awskms<\/em>replica_key in your Terraform configuration:<\/p>\n provider “aws” { resource “aws_kms_key” “primary” { description = “Multi-Region primary key” resource “aws_kms_replica_key” “replica” { In many cases, practitioners have used mechanisms such as creating aliases to build configurations that span across multiple AWS Regions. For example:<\/p>\n provider “aws” { provider “aws” { resource “aws_kms_key” “test” { description = “Multi-Region primary key” resource “aws_kms_replica_key” “test” { To migrate from a separate provider configuration for each Region to a single provider configuration block and per-resource region values you must ensure that Terraform state is refreshed before editing resource configuration:<\/p>\n Upgrade to version 6.0 provider “aws” { resource “aws_kms_key” “test” { description = “Multi-Region primary key” resource “aws_kms_replica_key” “test” { The Terraform AWS provider 6.0 is now available for use in the Terraform Registry. When upgrading to version 6.0 of the Terraform AWS provider, please consult the upgrade guide<\/a> on the Terraform Registry as it contains not only a list of changes but also examples. Because this release introduces breaking changes, we recommend pinning your provider version<\/a> to protect against unexpected results. <\/p>\n For the full list of updates in version 6.0, please refer to the summary of changes<\/a> on GitHub. To learn the basics of Terraform using this provider, follow the hands-on tutorials for getting started with Terraform on AWS<\/a> on our developer education platform. Interact with AWS services, including AWS Lambda<\/a>, Amazon RDS<\/a>, and AWS IAM<\/a> by following the AWS services tutorials<\/a>.<\/p>\n
\nRegion attribute injection<\/strong>: The region argument is added to all resources (except global resources) without requiring explicit schema changes.
\nGlobal resources exclusion<\/strong>: Services like IAM, CloudFront, and Route 53 remain unaffected as they operate globally.
\nTerraform plugin framework updates<\/strong>: Adjustments to the AWS API client mechanism support per-region API client mappings.
\nResource import enhancements<\/strong>: A new @<regionID> suffix allows importing of resources from different regions.
\nDocumentation and testing<\/strong>: Changes are documented at the provider level and tested to ensure backward compatibility.<\/p>\n
\n region = “us-east-1”
\n}<\/p>\n
\n cidr_block = “10.0.0.0\/16”
\n}<\/p>\n
\n region = “us-west-2”<\/p>\n
\n}<\/p>\n
\nresource “aws_vpc_peering_connection” “main” {
\n vpc_id = aws_vpc.main.id
\n peer_vpc_id = aws_vpc.peer.id
\n peer_region = “us-west-2”
\n auto_accept = false
\n}<\/p>\n
\nresource “aws_vpc_peering_connection_accepter” “peer” {
\n region = “us-west-2”<\/p>\n
\n auto_accept = true
\n}<\/p>\n
\n region = “us-west-2”
\n}<\/p>\n
\n region = “us-east-1”<\/p>\n
\n deletion_window_in_days = 30
\n multi_region = true
\n}<\/p>\n
\n description = “Multi-Region replica key”
\n deletion_window_in_days = 7
\n primary_key_arn = aws_kms_key.primary.arn
\n}<\/p>\nMigrating configuration to use the new region parameter<\/h2>\n
\n region = “us-east-1”
\n}<\/p>\n
\n alias = “peer”
\n region = “us-west-2”
\n}<\/p>\n
\n provider = aws.peer<\/p>\n
\n multi_region = true
\n}<\/p>\n
\n description = “Multi-Region replica key”
\n primary_key_arn = aws_kms_key.test.arn
\n}<\/p>\n
\nRun a Terraform plan in refresh-only mode<\/a> \u2014 terraform plan -refresh-only
\nRun a Terraform apply in refresh-only mode<\/a> \u2014 terraform apply -refresh-only
\nModify the affected resource configurations, replacing the provider meta-argument<\/a> with a region argument. For example:<\/p>\n
\n region = “us-east-1”
\n}<\/p>\n
\n region = “us-west-2”<\/p>\n
\n multi_region = true
\n}<\/p>\n
\n description = “Multi-Region replica key”
\n primary_key_arn = aws_kms_key.test.arn
\n}<\/p>\nGetting started<\/h2>\n