Customization of Landing zone : AWS Landing Zone Accelerator is failing while creating pipe line.

1

Did anyone use the AWS accelerator successfully to build the pipeline?

I am trying to customize the landzing zone using AWS accelerator, used Control Tower for prerequisites.

I am following steps mentioned at below link.

https://github.com/awslabs/landing-zone-accelerator-on-aws

But getting issue while AWSAccelerator-Pipeline pipe line execution, it passed for AWSAccelerator-Installer tough.

What can be the root cause as per our understanding it is failing in validation and considering all the OUs in the root not sure why it is considering all the OUs even if they are not controlled (registered) with Control Tower.

Error message.


AWSAccelerator-PrepareStack-1723*****-ap-southeast-2 | 55/98 | 2:11:58 PM | CREATE_IN_PROGRESS   | Custom::ValidateEnvironmentConfig                  | ValidateEnvironmentConfig/Resource/Default (ValidateEnvironmentConfigB40B464F) Resource creation Initiated
AWSAccelerator-PrepareStack-1723****-ap-southeast-2 | 55/98 | 2:11:58 PM | CREATE_FAILED        | Custom::ValidateEnvironmentConfig                  | ValidateEnvironmentConfig/Resource/Default (ValidateEnvironmentConfigB40B464F) Received response status [FAILED] from custom resource. Message returned: Error: Organizational Unit 'Projects OU' with id of 'ou-51e8-*****' was not found in the organization configuration.,Organizational Unit 'Projects OU/Temp2' with id of 'ou-51e8-****' was not found in the organization configuration.,Organizational Unit 'ctmarch16-ou1' with id of 'ou-51e8-*****' was not found in the organization configuration.,Organizational Unit 'QA Demo' with id of 'ou-51e8-****' was not found in the organization configuration.,Organizational Unit 'Org-UX' with id of 'ou-51e8-*****' was not found in the organization configuration.,Organizational Unit 'Prod OU2' with id of 'ou-51e8-*******' was not found in the organization configuration.,Organizational Unit 'Prod OU2/Temp' with id of 'ou-51e8-****** was not found in the organization configuration.
已提問 1 年前檢視次數 470 次
1 個回答
0

Got the above issue, aws accelerator consider all the OUs should be provided in the configurations files (organization_config.yaml) file in case we wants to ignore OUs we can add a flag for that account (flag ignore: true).

已回答 1 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南