Skip to content

feat!: Upgrade AWS provider and min required Terraform version to 6.0 and 1.10 respectively #436

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

bryantbiggs
Copy link
Member

@bryantbiggs bryantbiggs commented Jun 23, 2025

Description

List of backwards incompatible changes

  • Terraform v1.10.0 is now minimum supported version
  • AWS provider v6.0.0 is now minimum supported version
  • The default value for ami_ssm_parameter was changed from "/aws/service/ami-amazon-linux-latest/amzn2-ami-hvm-x86_64-gp2" to "/aws/service/ami-amazon-linux-latest/al2023-ami-kernel-default-x86_64". AL2 is approaching end of life.

Additional changes

Added

  • Support for creating a security group within the module; this is now the default behavior and can be disabled by setting create_security_group = false.
  • Support for region parameter to specify the AWS region for the resources created if different from the provider region.
  • Support for tagging spot instances

Modified

  • Variable definitions now contain detailed object types in place of the previously used any type.
  • Inline ebs_block_device argument has been removed in favor of ebs_volumes which is a map of EBS volumes created through aws_ebs_volume and aws_ebs_volume_attachment resources. This provides the same API as before, but allows for more flexibility without generating diffs when adding or removing EBS volumes as well as unintended changes to the volumes.
  • Correct tag precedence ordering (least specific to most specific)

Removed

  • The volume-attachment example has been removed since the module has been updated to use the corrected form of EBS volume creation and attachment (tl;dr - example is no longer useful).

Motivation and Context

Breaking Changes

  • Yes, see docs/UPGRADE-6.0.md for more details

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@bryantbiggs bryantbiggs force-pushed the feat/provider-update branch 2 times, most recently from 5178ca9 to 8ad7443 Compare June 23, 2025 22:19
@bryantbiggs bryantbiggs force-pushed the feat/provider-update branch from 8ad7443 to 50282b0 Compare June 24, 2025 02:22
@bryantbiggs bryantbiggs marked this pull request as ready for review June 24, 2025 18:49
@bryantbiggs bryantbiggs requested a review from antonbabenko June 24, 2025 18:49
Copy link
Member

@antonbabenko antonbabenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome!

@bryantbiggs bryantbiggs merged commit bfd5ed3 into terraform-aws-modules:master Jun 24, 2025
7 checks passed
@bryantbiggs bryantbiggs deleted the feat/provider-update branch June 24, 2025 19:29
antonbabenko pushed a commit that referenced this pull request Jun 24, 2025
## [6.0.0](v5.8.0...v6.0.0) (2025-06-24)

### ⚠ BREAKING CHANGES

* Upgrade AWS provider and min required Terraform version to `6.0` and `1.10` respectively (#436)

### Features

* Upgrade AWS provider and min required Terraform version to `6.0` and `1.10` respectively ([#436](#436)) ([bfd5ed3](bfd5ed3))
@antonbabenko
Copy link
Member

This PR is included in version 6.0.0 🎉

Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 25, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.