Which action should be taken to meet these requirements?
Automate using AWS Elastic Beanstalk to provision the AWS accounts, set up infrastructure, and integrate with AWS Organizations.
Create bootstrapping scripts in AWS OpsWorks and combine them with AWS CloudFormation templates to provision accounts and infrastructure.
Use AWS Config to provision accounts and deploy instances using AWS Service Catalog.
Use AWS Control Tower to create a template in Account Factory and use the template to provision new accounts.
Explanations:
AWS Elastic Beanstalk is designed for deploying and managing applications, not for account provisioning or governance. It does not integrate directly with AWS Organizations for account creation.
AWS OpsWorks is primarily used for configuration management and application deployment. While it can automate infrastructure setups, it is not ideal for provisioning AWS accounts or enforcing governance.
AWS Config is a service for tracking resource configurations and compliance, not for provisioning AWS accounts. AWS Service Catalog is used for managing predefined infrastructure, not account creation.
AWS Control Tower is specifically designed to set up and govern AWS environments across multiple accounts. The Account Factory feature allows for scalable, automated account creation with governance controls.
I categorize that the answer is:
Use AWS Control Tower to create a template in Account Factory and use the template to provision new accounts.
If I had to guess, I’d say the answer is:
Use AWS Control Tower to create a template in Account Factory and use the template to provision new accounts.