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
502 stars 396 forks source link

Accelerator Metadata Configuration resource name needs to be updated in documentation #498

Open joeldesaulniers opened 1 week ago

joeldesaulniers commented 1 week ago

Describe the bug The documentation related to the deployment of the Accelerator Metadata Configuration is incorrect. The documentation indicates that this resource should be named acceleratorMetadataConfig, which is incorrect. The correct resource name is acceleratorMetadata.

To Reproduce If you define the Accelerator Metadata Configuration within the global-config.yaml file usingacceleratorMetadataConfig, it simply does not work. No Metadata S3 logging bucket is created, no cross-account IAM role is created.

Expected behavior By defining it as acceleratorMetadata, it then works as expected and creates the Metadata S3 logging bucket and required cross-account IAM role.

Please complete the following information about the solution: Please update the documentation at the two following links to reflect the correct resource name. Simply change acceleratorMetadataConfig to acceleratorMetadata.

bo1984 commented 1 week ago

Hi Joel!

Thank you for reaching out and using the Landing Zone Accelerator on AWS (LZA) solution . I have opened an internal bug report for this issue. I will provide you with an update on when this has been fixed and released. If you have any other questions or concerns in the meantime, please do not hesitate to contact us.