1 Answer
- Newest
- Most votes
- Most comments
0
Thanks for reporting these issues. There are two problems. The first is that blueprints must be enabled in an associated account to successfully create an environment. Please check on the blueprint, it needs to be enabled in the account. Part of enabling the blueprint will create or specify the provisioning role and manage access role. As an SSO user, please choose accounts the blue print is enabled in before creating the environment.
The second issue where the environment can not be deleted is a defect. A fix will be released this week e.g. 10/13. Thank you for reporting it.
answered 7 months ago
Relevant content
- Accepted Answerasked a year ago
- asked 3 years ago
- asked 2 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Deleting an Environment as of 24th October still does not work. Produces same error. Similarly with the current interface it is impossible to verify and associated account without enabling the blueprint, so I dont think that is the solution. I believe there is an error here.