Gruntwork release 2026-02
Guides / Update Guides / Releases / 2026-02
This page is lists all the updates to the Gruntwork Infrastructure as Code
Library that were released in 2026-02. For instructions
on how to use these updates in your code, check out the updating
documentation.
Here are the repos that were updated:
Published: 2/24/2026 | Release notes
Published: 2/23/2026 | Release notes
Variables with default values no longer prompt users for interactive input unless using the new confirm attribute.
variables:
- name: AppName
type: string
default: "my-app"
confirm: true
- name: ContainerName
type: string
default: "container"
This ensures that dynamically determined values for variables won't cause errors during interactive generation and reduces the number of prompts users encounter while generating from a template interactively.
The length validation now uses the functional form length(min, max) instead of the previous length-min-max form.
All validations with parameters will use this functional form going forward.
The validation type regex(pattern) is now supported to validate variable values against regex patterns.
e.g.
- name: SlugName
type: string
description: URL-friendly project slug
validations:
- required
- length(3, 30)
- regex("^[a-z0-9-]+$")
Releases now support JavaScript runtimes through compiled WASM build targets.
Boilerplate now has a dedicated website at https://boilerplate.gruntwork.io to document the behavior of Boilerplate.
Full Changelog: https://github.com/gruntwork-io/boilerplate/compare/v0.11.1...v0.12.0
Published: 2/23/2026 | Release notes
Published: 2/23/2026 | Release notes
Published: 2/20/2026 | Release notes
Published: 2/13/2026 | Release notes
Published: 2/26/2026 | Release notes
Published: 2/12/2026 | Release notes
Published: 2/6/2026 | Release notes
Published: 2/3/2026 | Release notes
Published: 2/26/2026 | Release notes
Published: 2/23/2026 | Release notes
Published: 2/12/2026 | Release notes
Published: 2/12/2026 | Release notes
Published: 2/6/2026 | Release notes
Published: 2/6/2026 | Release notes
Published: 2/6/2026 | Release notes
Published: 2/3/2026 | Release notes
Published: 2/27/2026 | Release notes
🔩 This release contains some internal reworks around how we collect and process Terragrunt output during plan/apply, as well as adding the Terragrunt Run Report to Job artifacts for future use. There is additional internal Gruntwork telemetry around deploys being added, but we expect no user facing impact from this release.
Full Changelog: https://github.com/gruntwork-io/pipelines-workflows/compare/v4...v4.9.0
Published: 2/23/2026 | Release notes
Published: 2/12/2026 | Release notes
Published: 2/6/2026 | Release notes
Published: 2/3/2026 | Release notes
Published: 2/12/2026 | Release notes
Published: 2/11/2026 | Release notes
Published: 2/11/2026 | Release notes
Published: 2/6/2026 | Release notes
Published: 2/12/2026 | Modules affected: ecs-deploy-runner, infrastructure-deployer | Release notes
- Updated to Go 1.26 to address newly discovered CVEs
Published: 2/3/2026 | Release notes
- fix: save placeholder applyResults when patch runs in upgrade tester
Published: 2/2/2026 | Modules affected: build-helpers, ec2-backup, ecs-deploy-runner, jenkins-server | Release notes
- Additional module updates for AWS Provider v6 support
Published: 2/3/2026 | Release notes
- No changes with this release (from v0.59.0), 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: 2/3/2026 | Modules affected: data-stores, landingzone, networking, observability | Release notes
- Update modules to support AWS Provider v6.x
- Added full support for 10 new regions (ap-east-2, ap-south-2, ap-southeast-4/5/6/7, ca-west-1, eu-south-2, il-central-1, mx-central-1)
Published: 2/5/2026 | Modules affected: landingzone | Release notes
- make handle to update name of provisioned product for existing accounts
Published: 2/4/2026 | Modules affected: landingzone | Release notes
- Update modules to support AWS Provider v6.x
Published: 2/4/2026 | Modules affected: landingzone | Release notes
- Feat: Add missing regions to account baselines
Published: 2/12/2026 | Modules affected: backup-plan | Release notes
- dd ability to add selection tags optionally to backup-plan
Published: 2/10/2026 | Modules affected: redshift, rds-proxy | Release notes
- Replace deprecated snapshot_copy block with standalone resource
- Wait for RDS Proxy target health before connection tests
- Update DB subnet group script to refresh stale subnets
- Add missing DB subnet group config to TestRdsPostgresWithCloudWatchLogs
- Consolidate test infrastructure setup and fix test failures
- Run only affected tests to reduce CI cost and time
Published: 2/27/2026 | Release notes
- test fix: build AMI on tagged commits using GetCurrentGitRef to resolve branch name or tag in detached HEAD state
Published: 2/26/2026 | Modules affected: ecs-cluster | Release notes
- ecs-cluster: fix ECS container instance registration by defaulting IMDS hop limit to 2
- Test fixes
Published: 2/23/2026 | Modules affected: ecs-daemon-service, ecs-cluster, ecs-task-scheduler | Release notes
- Add Mixed Instances Policy with Spot support for ECS Cluster ASG
- Bug/484 ecs task scheduler fix name usage
- Test fixes
Published: 2/11/2026 | Modules affected: eks-cluster-managed-workers | Release notes
- add toggle to attach policies optionally to role used for control plane
Published: 2/6/2026 | Modules affected: eks-cluster-control-plane, eks-cluster-managed-workers, eks-cluster-workers | Release notes
This release removes the kubergrunt dependency from the EKS module, simplifying cluster management by leveraging native AWS EKS capabilities and EKS Managed add-ons.
Published: 2/2/2026 | Modules affected: openvpn-server | Release notes
- Fixing ldflags path for upgrade tests
- Update modules to support AWS Provider v6
Published: 2/27/2026 | Modules affected: cloudtrail-bucket | Release notes
- cloudtrail-bucket: fix inconsistent conditional result type errors in var.additional_bucket_policy_statements conditional fallback
Published: 2/11/2026 | Modules affected: data-stores | Release notes
- feat[s3-bucket]: Support AWS Provider V6
Published: 2/9/2026 | Modules affected: services/public-static-website | Release notes
- Bump
terraterraform-aws-static-assets to v1.2.0 for improved compatibility with AWS Provider v6.x
Published: 2/8/2026 | Modules affected: networking/vpc, services/eks-argocd, services/eks-cluster, services/eks-core-services | Release notes
- Bump
terraform-aws-eks to v3.4.0
- Add support for using an existing IAM role and security group for the EKS cluster control plane via new variables
cluster_iam_role_arn and cluster_security_group_id
> [!WARNING]
> #### IAM Role Immutability
> The cluster_iam_role_arn can ONLY be set during initial cluster creation. Changing the IAM role on an existing cluster will DESTROY and RECREATE the cluster (destructive operation). This is an AWS API constraint - IAM roles are immutable after cluster creation. Use this variable only for new clusters or when you specifically intend to recreate an existing cluster.
>
> The cluster_security_group_id can be updated in-place without cluster recreation via the AWS UpdateClusterConfig API.
Published: 2/2/2026 | Release notes
- No changes with this release (from v0.150.0), 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: 2/2/2026 | Modules affected: networking, services, base, data-stores | Release notes
- Update modules for AWS provider v6 support
- Bugfix: ecs services missing elb slow start
- Add disable_api_termination variable to ec2-instance module
Published: 2/9/2026 | Modules affected: s3-cloudfront, s3-static-website | Release notes
- Update modules for compatibility with AWS provider v6.x
Published: 2/6/2026 | Modules affected: vpc-app | Release notes
- LIB-4192 Fixing ldflags path for upgrade tests
- feat: add vpc_arn to outputs