3개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
1
You can decommission the Landing Zone, however some resources still going to be there, such as s3 buckets and CW logs.
https://docs.aws.amazon.com/controltower/latest/userguide/walkthrough-delete.html
답변함 2년 전
0
- Which account are you trying to deploy the Control Tower (CT) Landing Zone on? Is it the organizations management account? Is there any SCPs and /or restrictive policies applied to the account and the user / role?
- How long has the account been opened and is there any resources such as EC2 instances running in that account? If not please do launch 2 EC2 instances for about 30 mins.
- Have you reviewed the pre-requisites for deploy CT Landing Zone here?
- I would suggest you contact AWS Support in your support center so they can take a look into your account.
- It is possible to clean up the Landing Zone, besides the documentation, you might need to manually reset the root password and close the log archive and audit accounts. You will need two new email addressed for a brand new deployment. But like you mentioned before, it's a last resort to try only if no other causes can be identified.
답변함 2년 전
Hello @Json_S, I am facing the same issue. In my case, it is a new account, that was created over 3 days but never used.
I received the error and also launched an instance for over 30 minutes after seeing your suggestion. Also, unless Control tower is blocked by default, I don't think I am going over any quotas.
As I don't have a paid support plan, I am unable to contact the support directly, is there any other step that you suggest I take? I really would like to avoid have to recreate the setup.
관련 콘텐츠
AWS 공식업데이트됨 2년 전
Thank you, I was reading over the docs. I think I would need AWS to resolve the problem as it actually failed. The document says it won't resolve a failure. I was trying to take the easy way out "I thought" by using Tower. It may be better off just building my own landing zone.