Releases: aws-ia/terraform-aws-control_tower_account_factory
Releases · aws-ia/terraform-aws-control_tower_account_factory
1.6.5
- Bugfix: The
aft-invoke-customizations
step function now supports targeting nested OUs using the format "OU Name (ou-id-1234)" - Bugfix: Resolved an issue where AFT failed to correctly manage custom field SSM parameters for accounts with >10 custom fields defined
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
- AFT now collects anonymous operational metrics to help AWS improve the quality and features of AFT.
- For more information, including how to disable this capability, please see documentation here
1.5.2
- When generating credentials/aws profiles in account customization and global customization, the log statement for target account credential generation now properly refers to the target account ID
- Dynamically reference active partition for resource ARNs to align with AWS best practices
- Add README.md to
aft-account-request
terraform module which includes clarification on how the jinja files are used by AFT and supported ways in which you could leverage these
1.5.1
1.5.0
- Customization pipelines now share one CodeBuild container between the pre-api-helpers.sh, terraform apply, and post-api-helpers.sh stages. This allows sharing runtime variables or configurations between these stages. Both per-account and global customization workflows now use this pattern.
- An example use-case that this change enables is the use of private code repositories. This can be achieved by authenticating with your VCS in pre-api-helpers.sh, which makes it available at the time of terraform apply…
- Increased customization performance, runtime now spends less time provisioning containers.
- AFT Customization repositories no longer require the
aft-
prefix
Note: The updates to an $ACCOUNT_ID-customizations-pipeline
in the AFT management account will occur during the next invocation of the aft-invoke-customizations
stepfunction that targets the account(s) in question