Cant create environment in associated account domain: Provisioning Role Arn for environment blueprint id xxxxx not defined

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.