Quick Summary
The latest update to the AWS Terraform provider, version 6.32.1, includes four behavioral changes that affect various AWS resources, such as autoscaling groups, CloudWatch log delivery, DynamoDB tables, and ElastiCache replication groups. These changes aim to resolve specific issues, including errors during resource creation, loss of configuration settings, and validation errors. By addressing these problems, the update improves the overall stability and reliability of the provider. This release is part of the ongoing effort to refine the Terraform AWS provider, ensuring a smoother experience for developers working with AWS resources.
Changes by Severity
#### 🟢 Informational
The update includes fixes for several behavioral issues, including a "couldn't find resource" error during autoscaling group creation, a problem with the s3_delivery_configuration.suffix_path losing its prefix on update for CloudWatch log delivery, a perpetual diff issue with DynamoDB tables using a single range key on a global secondary index, and a false validation error when the auth_token references another resource for ElastiCache replication groups.
#### Editor's Note:
We consider this release a routine maintenance update, focusing on resolving specific pain points that developers may have encountered when working with the AWS Terraform provider. As part of the recent trend of refining the provider's behavior, this update is a step towards a more stable and predictable experience. When applying these changes, we recommend paying close attention to any resources that were previously affected by the "couldn't find resource" error, as the fix may alter the behavior of your Terraform configurations.
Migration Playbook
1. Review Autoscaling Group Configurations: Check your autoscaling group resources for any configurations that may have been affected by the "couldn't find resource" error during creation. Ensure that the wait_for_capacity_timeout is set appropriately to avoid any issues with the new behavior.
2. Update CloudWatch Log Delivery: If you are using CloudWatch log delivery with an s3_delivery_configuration.suffix_path, verify that the prefix is correctly set after updating to the new version. You can do this by checking the suffix_path attribute in your Terraform configuration.
3. Verify DynamoDB Table Configurations: For DynamoDB tables using a single range key on a global secondary index, review your key_schema configurations to ensure they are correctly defined. The update should resolve the perpetual diff issue, but it's essential to confirm that your configurations are accurate.
4. Check ElastiCache Replication Group Validation: If you are using an auth_token that references another resource for your ElastiCache replication group, verify that the validation error has been resolved. You can test this by running a Terraform plan or apply operation.
5. Test Your Terraform Configurations: After updating to the new version, thoroughly test your Terraform configurations to ensure that the changes have not introduced any unexpected behavior. Pay particular attention to resources that were previously affected by the fixed issues.
Verification Checklist
wait_for_capacity_timeout settingssuffix_path prefixes are correctly setkey_schema configurations for accuracyReferences
Last verified at: 2026-02-18T13:46:12.743642+00:00