Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot create new AWS accounts using Landing Zone #3

Closed
ShahradR opened this issue Mar 14, 2020 · 4 comments
Closed

Cannot create new AWS accounts using Landing Zone #3

ShahradR opened this issue Mar 14, 2020 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@ShahradR
Copy link
Owner

Using an AWS Contol Tower-managed Landing Zone solution, we are not able to create new accounts using the quick account provisioning wizard.

Specifically, when the page is loaded, we are immediately returned with the following error.

No launch paths found for resource

If we try completing the form and creating the account anyway, an additional error message is returned.

AWS Control Tower can’t create your account due to potential drift in your landing zone.

@ShahradR ShahradR added the bug Something isn't working label Mar 14, 2020
@ShahradR ShahradR self-assigned this Mar 14, 2020
@ShahradR
Copy link
Owner Author

This issue is currently blocking #1 – to complete the minimum viable product for the taskcat GitHub Action, we need to verify whether the action can deploy resources to an AWS account.

@ShahradR
Copy link
Owner Author

Based on the second error message, I tried resolving the configuration drift by repairing the landing zone, following this guide.

However, after the repair was complete, the problem persisted.

image

@ShahradR
Copy link
Owner Author

ShahradR commented Mar 14, 2020

Found someone with a similar issue on the AWS Developer Forum – running aws servicecatalog list-launch-paths --product-id prod-************* returns the same error as the console.

asciicast

Note that the product ID prod-************* has been obfuscated – you should use the same product ID returned in the console error message.

@ShahradR
Copy link
Owner Author

The issue was resolved by assigning an IAM group to the portfolio's permissions. This automatically created a launch path, and allowed the quick account provisioning wizard to complete.

It seems that a launch path is created automatically, and details which users can access what portfolios, given certain constraints. It's a bit complicated, so I will maybe follow-up with a more in-depth analysis. See this blog post by Ran Xing for more details and troubleshooting tips.

As far as this issue is concerned, however, adding the group to the portfolio has solved our problem.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant