A company is expanding its AWS usage and wants to provision separate accounts for each team with consistent baseline settings and governance. Account creation and bootstrapping must be scalable and efficient so new accounts are created with guardrails already applied. Which option best meets this need?

AWS Control Tower is specifically designed for setting up and governing a multi-account AWS environment, making it the ideal solution. Its Account Factory allows for automated, consistent provisioning of new accounts with pre-configured guardrails, security baselines, and network configurations. This directly addresses the need for scalable, efficient account creation with consistent baseline settings and governance. Automating with Elastic Beanstalk and Organizations is less suitable as Elastic Beanstalk is for deploying applications, not for account provisioning. AWS OpsWorks and CloudFormation can provision resources but lack the integrated governance and account-level guardrails that Control Tower provides out-of-the-box for new accounts. AWS Config is for evaluating resource configurations, not for provisioning accounts or deploying instances via Service Catalog, which is for managing approved IT services.