- Newest
- Most votes
- Most comments
Hi I am having the same issue. I've been able to request a dev account, which worked fine. Later the same day I request a staging account in the same manner, no account, no useful information, no failed steps or pipelines.
Why has AFT just stopped processing account requests with no changes being made to it? Where can I look to get detailed logs or information about such situations?
Are you still having this issue? If so, could you please post more information about the troubleshooting steps you have done so far? From my experience from recently deploying AFT is to carefully read the guide and don't miss some of the small details required. Also ensure that you fork/copy all of the example repos to have all thats needed.
Some things to check could be the post-deployment steps: https://docs.aws.amazon.com/controltower/latest/userguide/aft-post-deployment.html and the state machine customization steps: https://docs.aws.amazon.com/controltower/latest/userguide/aft-provisioning-framework.html
In the parameters block, if you are requesting an account in a nested OU, you have to specify the parent OU by ID. THEN it will work. In the root of the org you can leave it out. H
ope this helps.
control_tower_parameters = { AccountEmail = "aws+0@*******.co.uk" AccountName = "Staging" ManagedOrganizationalUnit = "Staging (ou-mjoh-xxxxxxxxx)" SSOUserEmail = "user.name@********.co.uk" SSOUserFirstName = "user" SSOUserLastName = "name" }
Relevant content
- AWS OFFICIALUpdated 16 days ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago