github awslabs/landing-zone-accelerator-on-aws v1.17.1

25 minutes ago

Important

We highly recommend that you keep your environments up to date by upgrading to the latest version. See Update the solution for the required actions to upgrade.

The Landing Zone Accelerator on AWS is designed and tested to work with the latest versions of Service Control Policies (SCPs) from the LZA Universal Configuration and the LZA CCCS Medium Configuration. Please review the latest changes in these repositories to ensure your SCPs align with the latest changes.

New Features

AWS European Sovereign Cloud CodePipeline Installer Support

The CodePipeline installer now supports the AWS European Sovereign Cloud (aws-eusc) partition. LZA uses eusc-de-east-1 as the partition's global Region and generates pipeline approval review links with the AWS European Sovereign Cloud console domain.

Release Software Bill of Materials

LZA releases now include CycloneDX Software Bills of Materials (SBOMs) for the installed source tree and final container archive. The release pipeline scans both SBOMs for vulnerabilities and publishes the following files with the GitHub release:

  • lza-v1.17.1-source.cdx.json
  • lza-v1.17.1-container.cdx.json
  • lza-v1.17.1-sbom-SHA256SUMS

The release process verifies the checksums before attaching these files to the GitHub release.

Bug Fixes

Identity Center Principal Assignment Cleanup

LZA now deletes the previous account assignment when an Identity Center assignment's principal is removed, replaced, or changed between principals and the deprecated principalId. Previously, LZA removed assignments only when target accounts were removed, which could leave the previous principal with access.

A matching assignment created outside LZA can also be deleted after it is declared in the LZA configuration. Removed principals that no longer exist in the identity store are skipped. Assignments left behind by earlier updates must be deleted manually. For assignments targeting many accounts, split principal changes across deployments to reduce the risk of reaching the 15-minute Lambda timeout.

External Pipeline Resource Retention

In external pipeline deployments, LZA now uses the management account as the credential account when applying stack resource retention to an external pipeline account that is also an LZA deployment target. Previously, the affected SecurityStack and NetworkAssociationsStack resources could be recorded as NOT_FOUND, leaving them without retention policies before migrated Amazon GuardDuty, Amazon Macie, or Transit Gateway resources were removed.

Existing NOT_FOUND retention records for the external pipeline account are retried with the corrected credentials. Records for other accounts remain final.

Shared AWS Organizations Policies During Rollback

A stack that shares an AWS Organizations policy with the stack that owns it no longer detaches or deletes the shared policy during rollback, stack deletion, or resource removal. The home Region OrganizationsStack owns tag policies, while the AccountsStack owns service control policies, resource control policies, and declarative policies.

Previously, a rollback in another stack could delete a shared policy across the organization and cause later pipeline runs to fail with PolicyNotFoundException. Affected deployments must follow the recovery procedure under Troubleshooting > Recovering shared AWS Organizations policies after a rollback in the Implementation Guide.

Closes #1245 (view issue).

VPC Flow Log Retention for V2 Stacks

When useV2Stacks is enabled, LZA now applies vpcFlowLogs.destinationsConfig.cloudWatchLogs.retentionInDays to VPC flow log groups created by V2 VPC stacks. Previously, these log groups always used the global cloudwatchLogRetentionInDays value.

When retentionInDays is omitted, the global value remains the default. Existing log groups adopt the configured retention period during the next pipeline run. Lowering the retention period permanently deletes log events older than the new value.

Closes #1275 (view issue).

Unsupported VPC Endpoint Policy Warnings

LZA now logs a warning during configuration validation and synthesis when a gateway or interface endpoint's policy, or the VPC's defaultPolicy, cannot be applied because the endpoint service does not support VPC endpoint policies.

The endpoint is still deployed without the policy, and the warning does not fail the pipeline. Set applyPolicy: false on the endpoint to acknowledge the unsupported policy and suppress the warning.

CloudWatch Logs Subscription Filters and KMS Key Retention

LZA can now add its subscription filter to LOG_GROUP subscription log groups that already have up to four filters. Previously, deployments failed when a log group already had two filters. A log group with all five permitted filters is skipped with a warning.

This release also retains the CloudWatch Logs KMS key when an initial LoggingStack deployment fails. Previously, rollback could schedule the key for deletion and leave log groups encrypted with an unusable key. Affected environments must follow the recovery procedure under Troubleshooting > Recovering log groups encrypted with a deleted accelerator CloudWatch Logs key in the Implementation Guide.

Accelerator Metadata Bucket Prefix Handling

The Accelerator Metadata Lambda now uses the configured bucket name prefix when the external pipeline qualifier retains its default value of aws-accelerator. Custom qualifiers that name buckets in external pipeline deployments remain supported.

Previously, LZA could derive the metadata bucket name from the pipeline qualifier instead of the configured bucket prefix, preventing the Lambda from accessing the expected bucket.

Closes #964 (view issue).

Central Logs KMS Parameter Role Trust Policy

The central logs bucket KMS ARN parameter access role now limits role assumption to accelerator-prefixed IAM roles in the organization. Previously, the role's caller restriction was evaluated after role assumption, which allowed any principal in the organization to assume the role.

Closes #1252 (view issue).

Changes

Duplicate Identity Center Assignment Validation

Configuration validation now warns when multiple identityCenterAssignments entries grant the same principal the same permission set on the same account. Editing, renaming, or deleting one of these duplicate entries can remove access that another entry still declares.

The warning does not fail the pipeline. To consolidate duplicate entries without interrupting access, remove the shared principals from one entry and then update the remaining entry so LZA recreates the assignment.

Configuration Reference Updates

The generated configuration reference and security documentation now provide more detail about resources and state that LZA retains, replaces, or deletes during configuration changes. The updates cover AWS Organizations policies, custom bucket policies, firewall configuration files, CloudWatch log groups, certificate replacements, delegated administrators, account-level subscription policies, and other resources that may require manual cleanup after an update.

Additional Resources

For full details, please see the CHANGELOG.

Don't miss a new landing-zone-accelerator-on-aws release

NewReleases is sending notifications on new releases.