A county GIS portal team wants merges to main to start automated te…

Question

A county GIS portal team wants merges to main to start automated tests, deploy to an Elastic Beanstalk test environment, then wait for a human gate before production. Which approach implements that commit-triggered path?

Accepted Answer

Use CodePipeline so a source commit starts CodeBuild tests, a CodeDeploy action to the Beanstalk test environment, then a manual approval before production deploy. — Picture a conveyor: merge drops the box on the belt, CodeBuild shakes it, CodeDeploy parks it in test Beanstalk, and a human stamps "go" before prod. That is CodePipeline doing the orchestration—not weekend SSH theater.

Answer

SSH into each Beanstalk instance after every merge and run unit tests by hand before copying files to production.

Answer

Schedule a weekly Lambda that rebuilds from a random branch without tying deploys to the merge event.

Answer

Publish directly from a developer workstation to production Beanstalk and skip the test environment.

A county GIS portal team wants merges to main to start automated tests, deploy to an Elastic Beanstalk test environment, then wait for a human gate before production. Which approach implements that commit-triggered path?

Short Explanation

Full Explanation