Gruntwork release 2025-05
Guides / Update Guides / Releases / 2025-05
This page is lists all the updates to the Gruntwork Infrastructure as Code
Library that were released in 2025-05. For instructions
on how to use these updates in your code, check out the updating
documentation.
Here are the repos that were updated:
Published: 5/28/2025 | Release notes
Published: 5/23/2025 | Release notes
Published: 5/1/2025 | Release notes
Published: 5/8/2025 | Release notes
Published: 5/2/2025 | Release notes
Published: 5/16/2025 | Release notes
Published: 5/20/2025 | Release notes
This release of Pipelines supports three new opt-in feature flags to improve the way we detect infra changes and execute Terragrunt in your repository. These features can be enabled by setting the following env vars to "true"
in your Pipelines configuration. We expect to enable these behaviors by default in a future major version of Pipelines.
-
PIPELINES_FEATURE_EXPERIMENT_AGGRESSIVE_CONSOLIDATION
Enabling this feature will cause more changes to be consolidated into a single run-all.
-
PIPELINES_FEATURE_EXPERIMENT_COLOCATED_FILE_UNIT_CHANGE_DETECTION
Enables changes to files colocated with a Terragrunt Unit (terragrunt.hcl
) to be detected as a ModuleChanged job.
-
PIPELINES_FEATURE_EXPERIMENT_MINIMIZE_BLAST_RADIUS
Enables Terragrunt queue-strict-include and queue-exclude-external by default.
You can read more detail about each of these feature flags here.
Added support for excluding files and directories from Pipelines runs. The ignore list can be added to your Pipelines config. Read more about the ignore list here.
Published: 5/8/2025 | Release notes
Published: 5/5/2025 | Release notes
Published: 5/28/2025 | Release notes
- Adds the
cloudtrail
module and modifies the cross-account-iam-roles
vars to address CIS findings IAM.18, S3.22 and S3.23
- Added
cloudtrail
module and modifies the cross-account-iam-roles
in:
- templates/devops-foundations-infrastructure-live-root/management/_global
- templates/single-account-baseline/{{ .AccountName }}/_global
No direct migration required. This change will result in a new role being created for AWSSupportAccess (IAM.18) and the cloudtrail
module will deploy for S3 logging (S3.22 and S3.23). Change should be non-impacting.
Published: 5/8/2025 | Release notes
-
Major cleanup update: Removed all legacy reference-architecture and devops foundations templates.
-
Updated devops foundations templates listed below to use root.hcl configuration file as their default to align with Terragrunt best practice:
devops-foundations-infrastructure-live-access-control
devops-foundations-infrastructure-live-access-control-accounts
devops-foundations-infrastructure-live-delegated
devops-foundations-infrastructure-live-delegated-v3
-
Use previous versions if you wish to keep using the deleted templates.
-
Set RootTerragruntFileName
as "terragrunt.hcl" to retain previous behaviour on devops foundations templates
Full Changelog: https://github.com/gruntwork-io/terraform-aws-architecture-catalog/compare/v2.13.0...v3.0.0
Published: 5/8/2025 | Release notes
- No changes with this release, moving to v1.x.x SemVer standard
This release marks a significant milestone for the module 🎉
We are officially adopting the Semantic Versioning (SemVer) standard, starting with version v1.0.0. Prior to this release, version tags only incremented patch and minor numbers. Moving forward, all releases should fully comply with the SemVer specification, providing clearer expectations for users regarding changes, compatibility, and upgrade paths.
With the v1.0.0 release, the library module is considered stable. This means that all subsequent changes in the v1.x.x series will be backward-compatible unless a new major version (v2.0.0) is released.
Version numbers will now follow the format MAJOR.MINOR.PATCH
MAJOR
: Incremented for breaking changes or incompatible API changes.
MINOR
: Incremented for new, backward-compatible features.
PATCH
: Incremented for backward-compatible bug fixes.
Users can now rely on the v1.x.x series to remain backward-compatible. Breaking changes should only occur in a future v2.0.0 release.
Each release will include detailed notes indicating whether changes are breaking, additive, or bug fixes, as per SemVer guidelines.
Published: 5/8/2025 | Modules affected: No | Release notes
- Bump golang.org/x/net from 0.36.0 to 0.38.0 in /test
Published: 5/8/2025 | Release notes
- No changes with this release, moving to v1.x.x SemVer standard
This release marks a significant milestone for the module 🎉
We are officially adopting the Semantic Versioning (SemVer) standard, starting with version v1.0.0. Prior to this release, version tags only incremented patch and minor numbers. Moving forward, all releases should fully comply with the SemVer specification, providing clearer expectations for users regarding changes, compatibility, and upgrade paths.
With the v1.0.0 release, the library module is considered stable. This means that all subsequent changes in the v1.x.x series will be backward-compatible unless a new major version (v2.0.0) is released.
Version numbers will now follow the format MAJOR.MINOR.PATCH
MAJOR
: Incremented for breaking changes or incompatible API changes.
MINOR
: Incremented for new, backward-compatible features.
PATCH
: Incremented for backward-compatible bug fixes.
Users can now rely on the v1.x.x series to remain backward-compatible. Breaking changes should only occur in a future v2.0.0 release.
Each release will include detailed notes indicating whether changes are breaking, additive, or bug fixes, as per SemVer guidelines.
Published: 5/8/2025 | Modules affected: valkey | Release notes
- modules/valkey: Sync Valkey engine-log configuration variables
- Bump golang.org/x/net to 0.38.0 in /test
Published: 5/1/2025 | Modules affected: rds-replicas, aurora, rds-proxy | Release notes
- Add a time_sleep to the destruction of the db subnet group
- Remove aurora serverless v1 as it's officially deprecated, fix serverless v2 test
- Fix TestLambdaRdsSnapshotDisable unit test failure
- Bump golang.org/x/net from 0.33.0 to 0.36.0 in /test
- Bump golang.org/x/net from 0.36.0 to 0.38.0 in /test
- Improve the documentation for rds-proxy module
- add cluster level insights
Published: 5/8/2025 | Release notes
- No changes with this release, moving to v1.x.x SemVer standard
This release marks a significant milestone for the module 🎉
We are officially adopting the Semantic Versioning (SemVer) standard, starting with version v1.0.0. Prior to this release, version tags only incremented patch and minor numbers. Moving forward, all releases should fully comply with the SemVer specification, providing clearer expectations for users regarding changes, compatibility, and upgrade paths.
With the v1.0.0 release, the library module is considered stable. This means that all subsequent changes in the v1.x.x series will be backward-compatible unless a new major version (v2.0.0) is released.
Version numbers will now follow the format MAJOR.MINOR.PATCH
MAJOR
: Incremented for breaking changes or incompatible API changes.
MINOR
: Incremented for new, backward-compatible features.
PATCH
: Incremented for backward-compatible bug fixes.
Users can now rely on the v1.x.x series to remain backward-compatible. Breaking changes should only occur in a future v2.0.0 release.
Each release will include detailed notes indicating whether changes are breaking, additive, or bug fixes, as per SemVer guidelines.
Published: 5/8/2025 | Modules affected: No | Release notes
- Bump golang.org/x/net from 0.36.0 to 0.38.0 in /test
Published: 5/14/2025 | Modules affected: eks-alb-ingress-controller-iam-policy | Release notes
- Update AWS LB Controller Module IAM Permissions to include
elasticloadbalancing:SetRulePriorities
to address 403 errors.
Published: 5/8/2025 | Modules affected: eks-k8s-karpenter | Release notes
- Update Karpenter Chart Mapping
postInstallHook
to map to correct Helm chart configuration value.
Published: 5/3/2025 | Release notes
- No changes with this release, moving to v1.x.x SemVer standard
This release marks a significant milestone for the module 🎉
We are officially adopting the Semantic Versioning (SemVer) standard, starting with version v1.0.0. Prior to this release, version tags only incremented patch and minor numbers. Moving forward, all releases should fully comply with the SemVer specification, providing clearer expectations for users regarding changes, compatibility, and upgrade paths.
With the v1.0.0 release, the library module is considered stable. This means that all subsequent changes in the v1.x.x series will be backward-compatible unless a new major version (v2.0.0) is released.
Version numbers will now follow the format MAJOR.MINOR.PATCH
MAJOR
: Incremented for breaking changes or incompatible API changes.
MINOR
: Incremented for new, backward-compatible features.
PATCH
: Incremented for backward-compatible bug fixes.
Users can now rely on the v1.x.x series to remain backward-compatible. Breaking changes should only occur in a future v2.0.0 release.
Each release will include detailed notes indicating whether changes are breaking, additive, or bug fixes, as per SemVer guidelines.
Published: 5/3/2025 | Modules affected: eks-k8s-karpenter | Release notes
- Use
name_prefix
instead of name for Karpenter AWS CloudWatch Event Rule resources to avoid name length errors when using de-provisioning queues.
- NOTE:
aws_cloudwatch_event_rule
resources created for Karpenter de-provisioning queues will be recreated with this change as moving from name
-> name_prefix
is a destructive action for the resource.
Published: 5/3/2025 | Modules affected: eks-aws-auth-merger | Release notes
- Bump golang.org/x/net from 0.36.0 to 0.38.0 in /modules/eks-aws-auth-merger/aws-auth-merger
- Bump golang.org/x/net from 0.36.0 to 0.38.0 in /test
Published: 5/1/2025 | Modules affected: keep-warm, lambda-edge | Release notes
- Bump golang.org/x/net from 0.34.0 to 0.36.0 in /test
- Bump axios from 1.7.4 to 1.8.2 in /examples/lambda-sam/javascript
- Update Nodejs runtime from 18.x to 22.x
Published: 5/8/2025 | Release notes
- No changes with this release, moving to v1.x.x SemVer standard
This release marks a significant milestone for the module 🎉
We are officially adopting the Semantic Versioning (SemVer) standard, starting with version v1.0.0. Prior to this release, version tags only incremented patch and minor numbers. Moving forward, all releases should fully comply with the SemVer specification, providing clearer expectations for users regarding changes, compatibility, and upgrade paths.
With the v1.0.0 release, the library module is considered stable. This means that all subsequent changes in the v1.x.x series will be backward-compatible unless a new major version (v2.0.0) is released.
Version numbers will now follow the format MAJOR.MINOR.PATCH
MAJOR
: Incremented for breaking changes or incompatible API changes.
MINOR
: Incremented for new, backward-compatible features.
PATCH
: Incremented for backward-compatible bug fixes.
Users can now rely on the v1.x.x series to remain backward-compatible. Breaking changes should only occur in a future v2.0.0 release.
Each release will include detailed notes indicating whether changes are breaking, additive, or bug fixes, as per SemVer guidelines.
Published: 5/6/2025 | Modules affected: alb | Release notes
- Bump golang.org/x/net from 0.33.0 to 0.36.0 in /test
- Bump golang.org/x/net from 0.36.0 to 0.38.0 in /test
- Expose SG Egress CIDR Blocks via a new variable allow_outbound_to_cidr_blocks
Published: 5/1/2025 | Release notes
- Bump golang.org/x/net from 0.33.0 to 0.36.0 in /test
- Bump golang.org/x/net from 0.36.0 to 0.38.0 in /test
Published: 5/6/2025 | Release notes
- No changes with this release, moving to v1.x.x SemVer standard
This release marks a significant milestone for the module 🎉
We are officially adopting the Semantic Versioning (SemVer) standard, starting with version v1.0.0. Prior to this release, version tags only incremented patch and minor numbers. Moving forward, all releases should fully comply with the SemVer specification, providing clearer expectations for users regarding changes, compatibility, and upgrade paths.
With the v1.0.0 release, the library module is considered stable. This means that all subsequent changes in the v1.x.x series will be backward-compatible unless a new major version (v2.0.0) is released.
Version numbers will now follow the format MAJOR.MINOR.PATCH
MAJOR
: Incremented for breaking changes or incompatible API changes.
MINOR
: Incremented for new, backward-compatible features.
PATCH
: Incremented for backward-compatible bug fixes.
Users can now rely on the v1.x.x series to remain backward-compatible. Breaking changes should only occur in a future v2.0.0 release.
Each release will include detailed notes indicating whether changes are breaking, additive, or bug fixes, as per SemVer guidelines.
Published: 5/8/2025 | Release notes
- No changes with this release, moving to v1.x.x SemVer standard
This release marks a significant milestone for the module 🎉
We are officially adopting the Semantic Versioning (SemVer) standard, starting with version v1.0.0. Prior to this release, version tags only incremented patch and minor numbers. Moving forward, all releases should fully comply with the SemVer specification, providing clearer expectations for users regarding changes, compatibility, and upgrade paths.
With the v1.0.0 release, the library module is considered stable. This means that all subsequent changes in the v1.x.x series will be backward-compatible unless a new major version (v2.0.0) is released.
Version numbers will now follow the format MAJOR.MINOR.PATCH
MAJOR
: Incremented for breaking changes or incompatible API changes.
MINOR
: Incremented for new, backward-compatible features.
PATCH
: Incremented for backward-compatible bug fixes.
Users can now rely on the v1.x.x series to remain backward-compatible. Breaking changes should only occur in a future v2.0.0 release.
Each release will include detailed notes indicating whether changes are breaking, additive, or bug fixes, as per SemVer guidelines.
Published: 5/8/2025 | Modules affected: No | Release notes
- Bump golang.org/x/net from 0.36.0 to 0.38.0 in /test
Published: 5/20/2025 | Modules affected: modules/networking/vpc, modules/services/eks-argocd, modules/services/eks-cluster, modules/services/eks-core-services | Release notes
- Bump
terraform-aws-eks
to v1.0.2
- Update Karpenter Chart Mapping
postInstallHook
to map to correct Helm chart configuration value.
- Update AWS LB Controller Module IAM Permissions to include
elasticloadbalancing:SetRulePriorities
to address 403 errors.
Published: 5/18/2025 | Modules affected: modules/networking/vpc, modules/services/eks-argocd, modules/services/eks-cluster, modules/services/eks-eks-core-services | Release notes
- Bump
terraform-aws-eks
to v0.79.0
- Expose new variable
karpenter_deprovisioning_queue_name
in services/eks-karpenter
module.
- NOTE: This version of
terraform-aws-eks
uses the name_prefix
attribute instead of the name
attribute for Karpenter AWS CloudWatch Event Rule resources to avoid name length errors when using de-provisioning queues. The aws_cloudwatch_event_rule
resources that are created for Karpenter de-provisioning queues will be recreated with this change as moving from name
-> name_prefix
is a destructive action for the resource. Please see the underlying EKS Library module release for details of the change
Published: 5/15/2025 | Modules affected: mgmt, networking, services | Release notes
Published: 5/6/2025 | Modules affected: networking | Release notes
- Updated modules/networking/alb to expose the allowed outbound CIDRs via a new variable allow_outbound_to_cidr_blocks
Published: 5/6/2025 | Modules affected: data-stores | Release notes
- Updated modules/data-stores/s3-bucket to expose the var transition_default_minimum_object_size
Published: 5/2/2025 | Modules affected: services | Release notes
- services/lambda: update to latest version of modules
Published: 5/1/2025 | Modules affected: services/asg-service | Release notes
- Bump golang.org/x/net from 0.36.0 to 0.38.0 in /test
- add param for asg name
Published: 5/20/2025 | Modules affected: cloudfront | Release notes
- [SME-3123] fix origin_access_identity path for s3_origin_config
Published: 5/8/2025 | Release notes
- No changes with this release, moving to v1.x.x SemVer standard
This release marks a significant milestone for the module 🎉
We are officially adopting the Semantic Versioning (SemVer) standard, starting with version v1.0.0. Prior to this release, version tags only incremented patch and minor numbers. Moving forward, all releases should fully comply with the SemVer specification, providing clearer expectations for users regarding changes, compatibility, and upgrade paths.
With the v1.0.0 release, the library module is considered stable. This means that all subsequent changes in the v1.x.x series will be backward-compatible unless a new major version (v2.0.0) is released.
Version numbers will now follow the format MAJOR.MINOR.PATCH
MAJOR
: Incremented for breaking changes or incompatible API changes.
MINOR
: Incremented for new, backward-compatible features.
PATCH
: Incremented for backward-compatible bug fixes.
Users can now rely on the v1.x.x series to remain backward-compatible. Breaking changes should only occur in a future v2.0.0 release.
Each release will include detailed notes indicating whether changes are breaking, additive, or bug fixes, as per SemVer guidelines.