- Newest
- Most votes
- Most comments
I apologize, but I don't have specific information about the issue you're experiencing with LZA 1.11.2 or the exact error you're encountering. However, I can provide some general guidance on account creation and troubleshooting in AWS environments.
For creating new AWS accounts, typically you would use AWS Service Catalog Account Factory if you're using AWS Control Tower. This process involves signing into your user portal, navigating to the AWS Account page, selecting the management account ID, and then using the Service Catalog console to launch the AWS Control Tower Account Factory product.
Regarding the issue with AWS Config not being enabled in the us-west-1 region for new accounts, this could be related to your Control Tower settings. Control Tower manages which regions are governed, and if us-west-1 is no longer activated, it may explain why AWS Config is not being set up there for new accounts.
For the specific error you're seeing with the ASEA-SecurityResourcesStack-us-west-1, it appears to be related to the absence of a Configuration Recorder. This is typically set up by AWS Config, so the root cause may indeed be that AWS Config is not properly enabled in that region.
To troubleshoot this issue:
- Check your Control Tower settings to ensure us-west-1 is properly activated if you need that region governed.
- Verify AWS Config settings in your management account and ensure it's properly set up for the regions you need.
- If you continue to encounter issues, you may need to reach out to AWS Support for more detailed assistance, as they would have more insight into your specific account configuration and the intricacies of LZA 1.11.2.
Remember that when creating new accounts or making significant changes to your AWS environment, it's important to ensure all prerequisites are met and that your settings align with your organizational requirements across all relevant regions.
Sources
Provision accounts with AWS Service Catalog Account Factory - AWS Control Tower
Troubleshooting issues with AWS account creation - AWS Account Management
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 months ago