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 available in public beta. Along with bugfixes, the latest update brings enhanced multi-region support and other workflow improvements. <\/p>\n
This post will explore the enhanced mult-region support features and announce the provider\u2019s latest downloads milestone.<\/p>\n
We are excited to announce that this release coincides with a new milestone: The Terraform AWS provider has surpassed 4 billion downloads.<\/p>\n
As we approach 5 billion downloads, 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. For example, we recently partnered to develop pre-written Sentinel policy sets for AWS<\/a> to simplify policy adoption and provide a turnkey governance solution for our customers. <\/p>\n With Terraform, HashiCorp aims to provide launch-day support for all AWS services, ensuring immediate access to the latest innovations. We also recommend you learn about the AWSCC provider<\/a> and compare it to the AWS provider<\/a>.<\/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 awsvpcpeeringconnectionaccepter 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 awskmsreplicakey in your Terraform configuration: <\/p>\n ### KMS Replica Key<\/p>\n #### Terraform AWS Provider v6 (and above)<\/p>\n “`terraform resource “aws_kms_key” “primary” { description = “Multi-Region primary key” resource “aws_kms_replica_key” “replica” { The Terraform AWS provider 6.0 pre-release is labeled “beta” and uploaded to the Terraform Registry as usual. It is important to note that users with permissive version constraints will not automatically use the new beta version. Instead, they will need to opt in by specifying the pre-release version<\/a> in their provider requirements<\/a>:<\/p>\n terraform { 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. The beta will run for six weeks. Please submit any feedback by creating an issue in the provider using the beta-feedback form<\/a>.<\/p>\n 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>\nEnhanced region support<\/h2>\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
\nprovider “aws” {
\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>\nGetting started<\/h2>\n
\n required_providers {
\n aws = {
\n source = “hashicorp\/aws”
\n version = “= 6.0.0-beta1”
\n }
\n }
\n}<\/p>\n