Updatestf-aws

Terraform AWS Provider: 13 New Features in Account Regions, Ecrpublic Authorization Token

v6.30.0 → v6.31.0Verified February 18, 2026

Impact Assessment

  • Severity rating: Moderate
  • This update brings a mix of new features and behavioral changes, primarily affecting AWS resources, with a notable deprecation of the expected_bucket_owner attribute across several S3 bucket configurations, which may require adjustments in existing Terraform configurations to ensure compatibility.

    • Detailed Breakdown

    #### Deprecation of expected_bucket_owner Attribute

  • What specifically changed: The expected_bucket_owner attribute has been deprecated in resources such as aws_s3_bucket_abac, aws_s3_bucket_accelerate_configuration, aws_s3_bucket_acl, and others.
  • Why this matters for production systems: The deprecation of this attribute means that configurations relying on it will need to be updated to avoid potential errors or compatibility issues in future versions.
  • Concrete migration steps: Review and update Terraform configurations to remove references to the expected_bucket_owner attribute where it has been deprecated. For example, in aws_s3_bucket_acl, ensure that the acl attribute is correctly configured without relying on expected_bucket_owner.

    • #### Introduction of New Resources

  • What specifically changed: New resources such as aws_account_regions, aws_ecrpublic_authorization_token, aws_cloudwatch_event_rule, and others have been added.
  • Why this matters for production systems: These new resources expand the capabilities of Terraform configurations, allowing for more comprehensive management of AWS resources.
  • Concrete migration steps: Explore the documentation of new resources (e.g., aws_cloudwatch_event_rule) to understand how they can be integrated into existing configurations to enhance functionality or replace deprecated resources.

    • #### Behavioral Changes

  • What specifically changed: Certain behavioral changes, like the restriction of listed buckets to the expected region in list-resource/aws_s3_bucket, have been implemented.
  • Why this matters for production systems: These changes can affect how resources are managed and listed, potentially impacting scripts or configurations that rely on specific behaviors.
  • Concrete migration steps: Review scripts or configurations that interact with affected resources (like aws_s3_bucket) and adjust them according to the new behaviors, ensuring compatibility and expected functionality.

    • #### Fixes and Improvements

  • What specifically changed: Fixes have been made to issues such as the AUTH to RBAC migration in aws_elasticache_replication_group.
  • Why this matters for production systems: These fixes improve the stability and functionality of Terraform when managing specific AWS resources.
  • Concrete migration steps: For resources like aws_elasticache_replication_group, verify that migrations from AUTH to RBAC are correctly handled, and test the updated behavior to ensure it aligns with production needs.

    • Editor's Note:

    As we review this update, it's clear that the Terraform AWS provider is undergoing significant enhancements, both in terms of new features and critical maintenance. We've seen a trend towards more robust resource management and deprecation of outdated attributes, which is in line with best practices for infrastructure as code. A practical tip for developers affected by the top change—the deprecation of expected_bucket_owner—is to prioritize reviewing and updating S3 bucket configurations to ensure a smooth transition and avoid future compatibility issues.

    Before You Upgrade

    1. Review the Terraform configuration files for any references to the deprecated expected_bucket_owner attribute.

    2. Test the removal of the expected_bucket_owner attribute in a non-production environment to identify potential issues.

    3. Explore the new resources and features introduced in this update to understand how they can enhance existing configurations.

    4. Update scripts or tools that interact with AWS resources to account for behavioral changes.

    5. Verify the compatibility of third-party modules or custom scripts with the updated Terraform version.

    6. Run terraform init and terraform plan to identify any configuration issues before applying changes.

    7. Use terraform state show to inspect the state of resources that may be affected by the update.

    8. Consult the Terraform and AWS documentation for detailed information on new resources and deprecated attributes.

    Sources & Timeline

  • [Release v6.31.0](https://github.com/hashicorp/terraform-provider-aws/releases/tag/v6.31.0)
  • [Release v6.30.0](https://github.com/hashicorp/terraform-provider-aws/releases/tag/v6.30.0)

    • Last verified: 2026-02-18T13:46:19.333921+00:00

    📎 Sources