https://github.com/gruntwork-io/boilerplate/pull/98: Implemented the ability to enforce boilerplate version when processing a template. You can now specify a version constraint in your boilerplate templates using the required_version config.
https://github.com/gruntwork-io/boilerplate/pull/92: Fixed bug where boilerplate continuously attempts to render templates defined in variable default value. This prevented rendering values that targeted go templates, like GitHub Actions.
Updated the vpc-mgmt-network-acls and vpc-app-network-acls modules to expose the ability to configure the initial rule number used for the rules. This allows a user to set a sufficiently high number to provide more head room for inserting higher priority rules.
Updated the macie module to allow configuring and managing the Macie CloudWatch Log Group within Terraform. This allows a user to configure encryption settings for the Log Group or retention settings.
Exposed configuration parameters for restricting IMDS endpoints on EC2 instances in ECS cluster. Refer to the new enable_imds and use_imdsv1 input parameters for more information.
Add support for managing EKS add-ons. Note that customized VPC CNI configurations (e.g., enabling prefix delegation) is not fully supported with add-ons as the automated add-on lifecycles could potentially undo the configuration changes. As such, it is not recommended to use EKS add-ons if you wish to use the VPC CNI customization features.
Exposed the ability to configure detailed monitoring per ASG, instead of only on all ASGs. This change is only backward incompatible if you were using the asg_enable_detailed_monitoring input variable - refer to the migration guide down below for more info.
The logs/load-balancer-access-logs module has been updated to support the recently changed private-s3-bucket module in terraform-aws-security, which now supports the Terraform AWS 4.x provider.
The openvpn-server module has been updated to support the recently changed private-s3-bucket module in terraform-aws-security, which now supports the Terraform AWS 4.x provider.
Exposed the ability to specify additional service principals that should be granted for CloudTrail key. This is useful for granting access to additional services for different needs, such as to CloudWatch for setting up log metric filters correctly.
Exposed ability to set up periodic background job to invoke ecs-deploy-runner. This can be used to run various tasks on a periodic basis in the background, such as running terragrunt run-all plan on a regular basis to detect infrastructure drift.
Exposed ability to configure CloudWatch subscriptions for services/lambda.
Enabled detailed monitoring for EKS Managed Node Group and self managed ASG instances. You can configure this using the new parameters to configure it.
Update various dependencies:
terraform-aws-lambda to v0.18.2
terraform-aws-eks to v0.50.1
terraform-aws-openvpn to v0.22.0
terraform-aws-ci to v0.45.4
Updated versions of tools installed in the jenkins server by default
helm to v3.8.0
terraform to v1.1.7
packer to v1.8.0
terragrunt to v0.36.3
Minor simplification of a local variable in account-baseline-root
Updated miscellaneous dependencies used in Terratest (no impact to modules)
The vpc-flow-logs module has been updated to support the recently changed private-s3-bucket module in terraform-aws-security, which now supports the Terraform AWS 4.x provider.
Point your module source to this release (v0.21.0), run terraform init -upgrade, and run terraform apply.
When you run terraform apply there should be no destroyed or recreated resources. You will see newly created resources and sometimes in-place modifications.
This is a functionally backward compatible upgrade, verified with partially automated upgrade testing. Upgrade testing was done to ensure that running init/plan/apply on previously deployed modules will not run into issues when you upgrade to this version of the modules.
No configuration changes are required.
The AWS provider version must be bumped to at least 3.75.0.
You can bump the provider by running terraform init with the -upgrade flag, as in terraform init -upgrade. See HashiCorp's guide on upgrading providers for more details.
Updated type table documentation for the additional_s3_bucket_policy_statements input variable.
Updated the vpc-mgmt-network-acls and vpc-app-network-acls modules to expose the ability to configure the initial rule number used for the rules. This allows a user to set a sufficiently high number to provide more head room for inserting higher priority rules.
Added the ability to configure additional bucket policies on the VPC flow logs bucket using the new additional_s3_bucket_policy_statements input variable.