search

awslabs / landing-zone-accelerator-on-aws

Deploy a multi-account cloud foundation to support highly-regulated workloads and complex compliance requirements.
https://aws.amazon.com/solutions/implementations/landing-zone-accelerator-on-aws/
Apache License 2.0
529 stars 418 forks source link

OUs not deleted when removed from organization-config.yaml #490

Open tkudlicki opened 2 months ago

tkudlicki commented 2 months ago

Describe the bug OUs created/registered in AWS Control Tower with LZA through organization-config.yaml are not deleted when removed from configuration file.

To Reproduce

  1. Add new OU(s) to organization-config in Control Tower enabled environment and release change to CodePipeline
  2. OU(s) are successfully created and registered in Control Tower
  3. Remove recently added OU from organization-config and rerun CodePipeline
  4. Pipeline fails at the Prepare stage
  5. Manually delete OU(s) from Control Tower
  6. Retry Prepare stage and pipeline successfully completes

Expected behavior Expectation was that resources created by the LZA would be deleted when removed from the configuration files.

Please complete the following information about the solution:

bo1984 commented 2 months ago

Hi Todd! Thank you for utilizing the Landing Zone Accelerator on AWS (LZA) solution. I have filed a feature request for this issue as the Create Organization Unit feature for LZA didn't include the logic to remove the Organization Unit. I will keep this issue open for further correspondence as the issue is evaluated in our backlog.