Releases: aws-ia/terraform-aws-control_tower_account_factory
Releases Β· aws-ia/terraform-aws-control_tower_account_factory
1.18.1
1.18.0
1.17.1
1.17.0
1.16.1
1.16.0
1.15.1
- Bug fix: Fix an issue where enabling optional CMK encryption for CloudWatch log groups could fail due to KMS policy propagation delays
- Improved
terraform planoutput clarity by removing unnecessary configuration differences for DynamoDB global secondary indexes
1.15.0
- Add optional KMS encryption for CloudWatch log groups and SNS topics using the AFT-created customer managed key (CMK). This encryption can be enabled at the time of deployment using the
cloudwatch_log_group_enable_cmk_encryptionandsns_topic_enable_cmk_encryptionvariables. Learn more about using CMK encryption for Cloudwatch log groups and SNS topics here. (#396)- When first enabling CMK encryption for CloudWatch log groups, an AssociateKmsKey error may occur due to eventual consistency in an updated policy. If this occurs, re-run
terraform apply.
- When first enabling CMK encryption for CloudWatch log groups, an AssociateKmsKey error may occur due to eventual consistency in an updated policy. If this occurs, re-run
- Enable changing CodeBuild compute type, using variable
aft_codebuild_compute_type(#474, #560) - Add new Terraform outputs for DynamoDB table, IAM role, S3 bucket name, KMS Key, Step Function, and SNS Topic ARNs (#81, #84)
- Require SSL for connections to S3 buckets (#300)
- Change DynamoDB tables to on-demand capacity mode, for more efficient utilization (#359, #497)
- Fix error preventing deployment in regions where the SSM global infrastructure parameter is not supported (#501)
- Improved error handling for missing Jinja2 templates in account request and customizations pipelines (#349)
- Update Lambda function dependencies
requests2.32.4boto3/botocore1.39.3
1.14.1
- Fix bug, impacting environments with variable
aft_enable_vpc=falseand no VPCs present, which caused Terraform plan and apply actions to fail.
1.14.0
- Add support for customer provided VPCs at the time of deployment. Learn more about deploying AFT in your own VPC here. (#192)
- Update VPC endpoints to support AWS Organizations when deploying in the
us-east-1AWS Region. (#452) - Add support for providing a project name to deploy AFT workspaces into. This functionality is applicable to Terraform Enterprise and HCP Terraform (formerly Terraform Cloud) customers. (#519, #447, #342)
- Add support for providing customer-defined tags to AFT resources. (#466)