The company has many apps built with different languages and frameworks, running on-premises across various OSs. Each team has its own release process. The company wants centralized source control, a consistent automated delivery pipeline, and minimal infrastructure maintenance after migrating to AWS. What approach meets these goals?

This approach provides centralized source control with CodeCommit, a consistent automated delivery pipeline using CodeBuild, ECR, CodeDeploy, and ECS, and minimal infrastructure maintenance with Fargate. Each application having its own repository is a best practice for independent development and deployment. Building Docker images standardizes the build process across different languages and frameworks. Deploying to ECS with Fargate eliminates the need to manage underlying EC2 instances, meeting the minimal infrastructure maintenance goal. Incorrect options: Deploying to "one centralized application server" creates a single point of failure and bottleneck, contradicting scalability and resilience goals. Merging all application code into branches of a single repository is not a best practice for independent application development. Building applications "one at a time" is vague and doesn't specify a standardized output. Deploying to "one centralized application server" has the same drawbacks as above. Creating an AMI for each server and using CloudFormation StackSets to provision EC2 fleets still requires managing EC2 instances, which is not "minimal infrastructure maintenance" compared to Fargate.