Terraform 0.14 upgrade: We have verified that this repo is compatible with Terraform 0.14.x!
From this release onward, we will only be running tests with Terraform 0.14.x against this repo, so we recommend updating to 0.14.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.14.x.
Once all Gruntwork repos have been upgrade to work with 0.14.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Many other bug fixes and improvements, including:
Bump to latest Service Catalog version
Enable encryption by default in a few places where it wasn't enabled already
A number of CI / CD and Jenkins fixes
Switch to main branch from master
Update internal references to the new repo naming scheme
Multitude of updates and fixes, including latest version of the service catalog, container image building for the deploy runner, app CI/CD, improved Jenkins Support, Elasticsearch blueprint, EKS bug fixes, and more.
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
This releases enable encryption by default for the Jenkins EBS volume. Previously, the EBS volume was not encrypted by default. Unless you want to destroy to recreate your Jenkins data EBS volume, you MUST follow the migration guide below.
Terraform 0.14 upgrade: We have verified that this repo is compatible with Terraform 0.14.x!
From this release onward, we will only be running tests with Terraform 0.14.x against this repo, so we recommend updating to 0.14.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.14.x.
Once all Gruntwork repos have been upgrade to work with 0.14.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Terraform 0.14 upgrade: We have verified that this repo is compatible with Terraform 0.14.x!
From this release onward, we will only be running tests with Terraform 0.14.x against this repo, so we recommend updating to 0.14.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.14.x.
Once all Gruntwork repos have been upgrade to work with 0.14.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Made some verifications for AWS Config required + add a comment with which CIS recommendation that belongs
Add outputs from the Benchmark filters to the Cloudtrail module
Add variable kms_key_already_exists for Cloudtrail module, there was an error where the var.kms_key_arn != null was invalid due kms_key_arn being an output from another module. The same variable exists in terraform-aws-security.
Add comments to IAM Groups around which recommendation belongs the hard-coded value
This release updates versions of several underlying modules, including several backwards incompatible upgrades. Please see the Migration guide section for manual steps necessary to perform the upgrade.
⚠️ This is a backwards incompatible upgrade. Please follow the instructions in the linked Release Notes pages to upgrade! If you are upgrading across multiple backwards incompatible versions (e.g., v0.3.0 to v0.6.0), you MUST check the release notes for every release in between too! ⚠️
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Terraform 0.14 upgrade: We have verified that this repo is compatible with Terraform 0.14.x!
From this release onward, we will only be running tests with Terraform 0.14.x against this repo, so we recommend updating to 0.14.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.14.x.
Once all Gruntwork repos have been upgrade to work with 0.14.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Fix health check and timeout settings for the target groups created by ecs-service. Depending on the protocol you're using (e.g., TCP, UDP, TLS, etc), only certain values are permitted. The AWS docs are unclear on this, but we've done our best to implement the required rules.
Remove var.environment_name from ecs-service and ecs-daemon-service. This was only used to name the IAM resources created within the modules, but was confusingly named. The functionality of the variable has been replaced with the following three, targeted variables:
var.custom_iam_role_name_prefix for the IAM role used by the ECS tasks.
var.custom_task_execution_name_prefix for the IAM role used by ECS to spawn the tasks.
var.custom_ecs_service_role_name for the IAM role used by the ECS service to access load balancers.
Refer to the migration guide to avoid recreating the IAM roles when updating to this release.
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Terraform 0.14 upgrade: We have verified that this repo is compatible with Terraform 0.14.x!
From this release onward, we will only be running tests with Terraform 0.14.x against this repo, so we recommend updating to 0.14.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.14.x.
Once all Gruntwork repos have been upgrade to work with 0.14.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Note that Terraform 0.14 seems to have exposed EKS authentication expiry issues more than previous versions, so when upgrading to this version, we recommend following the migration guide below.
The naming logic of the default Fargate execution IAM role has been modified to support longer cluster names. You can now directly set the IAM role name using the new custom_fargate_iam_role_name input variable. Note that the default name has also been shortened, using the suffix -fargate-role instead of -default-fargate-execution-role. To avoid recreating the IAM role, you can set var.custom_fargate_iam_role_name to CLUSTER_NAME-default-fargate-execution-role.
Update documentation to use the new repository names in cross references.
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Terraform 0.14 upgrade: We have verified that this repo is compatible with Terraform 0.14.x!
From this release onward, we will only be running tests with Terraform 0.14.x against this repo, so we recommend updating to 0.14.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.14.x.
Once all Gruntwork repos have been upgrade to work with 0.14.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Terraform 0.14 upgrade: We have verified that this repo is compatible with Terraform 0.14.x!
From this release onward, we will only be running tests with Terraform 0.14.x against this repo, so we recommend updating to 0.14.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.14.x.
Once all Gruntwork repos have been upgrade to work with 0.14.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
You can now use Docker images with the lambda module by specifying the new input variables image_uri, entry_point, command, and working_directory.
We renamed all our repos to use HashiCorp's naming convention (terraform-<cloud>-<name>, e.g., terraform-aws-vpc), so we went through each repo and updated all the internal references. This should not affect functionality.
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Add alb_name length validation. The alb_name variable will now only accept strings that are a maximum of 32 characters in length. This is a requirement imposed by the AWS API - so catching these issues on the client side prevents runtime errors. However, since native Terraform variable validation was released in v0.13.0, you will need to use at least Terraform v0.13.0 (or greater) going forward once you begin using this release.
Enhance documentation to clarify that if you are requesting a certificate for domain X but attaching it to a hosted zone whose name does not exactly match X, then you must specify hosted_zone_id in your acm tls certificate input map within var.acm_tls_certificates.
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
You can now configure custom auth settings for the nested provider block within the route53-health-check-alarms module using the new input variables provider_role_arn, provider_external_id, provider_session_name, provider_profile, and provider_shared_credentials_file.
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
You can now customize the mssfix value used in the openvpn config that is downloaded by openvpn-admin by using the --mssfix flag. Additionally, the openvpn-admin command will automatically identify the optimal mssfix value to use for the client machine when omitted.
Terraform 0.14 upgrade: We have verified that this repo is compatible with Terraform 0.14.x!
From this release onward, we will only be running tests with Terraform 0.14.x against this repo, so we recommend updating to 0.14.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.14.x.
Once all Gruntwork repos have been upgrade to work with 0.14.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Terraform 0.14 upgrade: We have verified that this repo is compatible with Terraform 0.14.x!
From this release onward, we will only be running tests with Terraform 0.14.x against this repo, so we recommend updating to 0.14.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.14.x.
Once all Gruntwork repos have been upgrade to work with 0.14.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Use created Organization ID as default for var.cloudtrail_organization_id. Now the account-baseline-root module can set up Cloudtrail both at the root-account level and organization-wide level.
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
You can now attach IAM policies (AWS managed, customer managed, and inline policies) directly to user in the iam-users module. Previously you were only able to attach IAM groups to the created users. Refer to the updated variable description for more details.
iam-users module is now robust to changes in the Access Key.
You can now enable access logging for the CloudTrail S3 bucket in account-baseline-root using the new enable_cloudtrail_s3_server_access_logging input variable.
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Use created Organization ID as default for var.cloudtrail_organization_id. Now the account-baseline-root module can set up Cloudtrail both at the root-account level and organization-wide level.
The CloudWatch alarm variables enable_cloudwatch_alarms and alarms_sns_topic_arn are now properly recognized. Previously these variables were ignored and no alarms for the ASG were being configured.
You can now configure the name of the Target Group using the target_group_name in the object passed to the server_ports input. This is useful when migrating an existing target group into the service catalog module.
Adding module-level flags to allow enabling or disabling of aws-config, iam-groups, iam-cross-account-roles modules. The default value of the enable_* flags is set to true, so using or calling these modules is not expected to change.
Add variable validation to alb_name to guard against the limit of 32 characters for ALB names
Fix bug in ec2-baseline where it incorrectly detected that dpkg was not available.
Add sensible defaults for ssh_grunt_iam_group and ssh_grunt_iam_group_sudo to the bastion-host and jenkins modules.
You can now configure a PodDisruptionBudget for your Kubernetes service deployed with the k8s-service module using the min_number_of_pods_available input variable.
You can now selectively disable the services that are deployed with eks-core-services using the new enable variables: var.enable_fluent_bit, var.enable_alb_ingress_controller, var.enable_external_dns, and var.enable_cluster_autoscaler. NOTE: This feature depends on Terraform 0.13.0 and above. If you are using Terraform 0.12, you must first upgrade to Terraform 0.13 to take advantage of this.
You can now control annotations and labels for the autoscaler service in eks-core-services using the new input variables cluster_autoscaler_pod_annotations and cluster_autoscaler_pod_labels, respectively.
Fix a bug in the output variables of the route53 module that, depending on the inputs you passed in, could lead to an "Inconsistent conditional result types" error.
Allows wildcard domains to be passed in the subject_alternative_names, making it easier to request a single ACM certificate that protects both the apex domain (example.com) AND the first level of subdomains (*.example.com). To achieve this, request example.com in the key of your var.public_zones map and pass *.example.com in the subject_alternative_names list for the same entry:
NOTE: Starting this release, it is no longer possible to disable the creation of ACM certificates on the domains that are managed by the module. We introduced back the ability to disable ACM certificate creation in v0.44.5. It is advised to upgrade to at least that version if you want to avoid managing ACM certificates in this module.
Encryption is now enabled by default for Elasticsearch
Encryption is now by default for the Jenkins EBS volume.
All Packer templates now enable encryption by default for the root volume of the image.
The sns-topics module now accepts a kms_master_key_id and a list of allow_publish_services that allow the given AWS services to publish to the SNS topic.
Terraform 0.14 upgrade: We have verified that this repo is compatible with Terraform 0.14.x!
From this release onward, we will only be running tests with Terraform 0.14.x against this repo, so we recommend updating to 0.14.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.14.x.
Once all Gruntwork repos have been upgrade to work with 0.14.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
All modules that were exporting CloudWatch dashboard metric widgets now also expose all the widgets in a single list output all_metric_widgets. This makes it easier to construct dashboards for specific services.
The jenkins module will now force https protocol for the ALB. Previously, the jenkins ALB was accessible under both http (port 80) and https (port 443). Now the ALB will automatically redirect to https when accessed under http.
The default version of Jenkins installed with the jenkins-server packer template is now 2.277.2 (previously 2.263.4). The default version of Terraform installed with the jenkins-server packer template is now 0.13.6 (previously 0.12.21).
The domain settings for openvpn-server now allow you to specify a custom domain.
account-baseline-app now has a number of conditional variables that can be used to enable/disable the creation of resources.
account-baseline-app now has the option to automatically deploy the iam-access-analyzer-multi-region module inline with the other account baselines. Note: this is disabled by default.
adds a number of conditional variables to the App Account Baseline in order to override the creation of resources with their CIS-compatible variants.
Update dependency gruntwork-io/terraform-aws-eks to v0.35.2. You can now configure additional output streams for fluent-bit on the eks-core-services module.
Update dependency gruntwork-io/gruntwork-installer to v0.0.36
Update dependency gruntwork-io/kubergrunt to v0.6.12
Update dependency gruntwork-io/terraform-aws-eks to v0.35.1 (was v0.33.1). This is a backward incompatible change. This update renames the default Fargate Execution IAM role that gets created by the eks-cluster-control-plane module. To avoid recreating the IAM role, you need to configure custom_default_fargate_iam_role_name to be <CLUSTER_NAME>-default-fargate-execution-role.
Update dependency gruntwork-io/terragrunt to v0.28.19
Remove unused variables (allow_requests_from_public_alb, include_internal_alb, enable_cloudwatch_alarms). If you were configuring these, you will need to remove them from your module call.
enable_ecs_cloudwatch_alarms, enable_cloudwatch_metrics, and enable_cloudwatch_log_aggregation now default to true like all the other modules in the Service Catalog. Set to false if you were using the default values.
Remove redundant cloudwatch logs aggregation IAM policy attachment.
Update dependency gruntwork-io/terraform-aws-monitoring to v0.26.1
Add ability to specify the encryption configuration for the images in the ECR repo
Update dependency gruntwork-io/kubergrunt to v0.6.11
Update dependency gruntwork-io/terraform-aws-security to v0.46.4
Update dependency gruntwork-io/terratest to v0.32.21
Address various inconsistencies in the ecs-service module:
Cleaned up health check related parameters to distinguish between those config for the Route 53 health check and those for the ALB.
Remove unused IAM role (aws_iam_role.ecs_task_execution_role)
Expose custom IAM role name prefixes.
Adjust required variables: ecs_cluster_name is now required, since it results in errors when set to null and ecs_node_port_mappings, which is only used in special circumstances, now defaults to null.
Update dependency gruntwork-io/terraform-aws-cache to v0.13.0 (previously v0.11.0)
Update dependency gruntwork-io/terraform-aws-security to v0.46.0 (previously v0.45.1)
Update dependency gruntwork-io/terratest to v0.32.18 (previously v0.32.10)
Update dependency gruntwork-io/terraform-aws-ecs to v0.25.3 (previously v0.25.1)
Update dependency gruntwork-io/terragrunt to v0.28.18 (previously v0.28.16)
Update dependency gruntwork-io/terraform-aws-server to v0.11.0 (previously v0.10.1)
Update dependency gruntwork-io/terraform-aws-eks to v0.33.1 (previously v0.32.4)
Update dependency gruntwork-io/terraform-aws-asg to v0.12.1 (previously v0.11.2)
Update dependency gruntwork-io/terraform-aws-data-storage to v0.18.1 (previously v0.17.3)
Update dependency gruntwork-io/terraform-aws-vpc to v0.14.4 (previously v0.13.1)
You can now configure the SSL protocol and origin protocol policy for CloudFront when it access the S3 bucket using the bucket_origin_config_protocol_policy and bucket_origin_config_ssl_protocols variables.
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
You can now specify lifecycle rules for the S3 bucket using the new lifecycle_rules input variable.
You can now automatically generate a random suffix for the S3 bucket name by setting the add_random_id_name_suffix input variable to true. This is helpful in ensuring that your S3 bucket name is globally unique.
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform 0.15.x!
From this release onward, we will only be running tests with Terraform 0.15.x against this repo, so we recommend updating to 0.15.x soon!
To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.15.x.
Once all Gruntwork repos have been upgrade to work with 0.15.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
Enable encryption by default: With this release, we are enabling encryption by default for all EBS volumes (including the root volume). This is a change we are making across all our repos. See the migration guide for upgrade instructions.