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 a platform-as-a-service for deploying and managing applications, not for provisioning AWS accounts or managing governance and compliance.
AWS OpsWorks is a configuration management service, typically used for application deployment, not for provisioning AWS accounts or managing governance.
AWS Config is a service for monitoring and auditing resource configurations. It does not directly provision accounts or deploy instances. AWS Service Catalog is for managing resources, not for creating accounts.
AWS Control Tower provides automated account provisioning with governance controls using Account Factory. It is designed for creating and managing AWS accounts with a defined baseline and guardrails, making it the most scalable and efficient option.
From what I’ve heard, the answer is:
Use AWS Control Tower to create a template in Account Factory and use the template to provision new accounts.