Add an ECS deploy stage, output imagedefinitions.json, and run connectivity checks from a Lambda action stage

Why the Answer Is Correct

Three additions to the existing pipeline satisfy the requirements with the least management overhead. First, the image build stage is updated to output an imagedefinitions.json file that references the new image tag, because that file is how a pipeline conveys the image version to the deployment action; without it the deploy stage would not know which image to roll out (D). Second, a deploy stage is added with Amazon ECS as the action provider, which deploys the new service revision to the existing ECS cluster with no additional deployment configuration, keeping management minimal compared with introducing CodeDeploy (A). Third, an AWS Lambda function that runs connectivity checks and API calls against the service is integrated as a Lambda action stage, so the integration tests execute automatically as part of the pipeline with no separate test framework or infrastructure to run and maintain (E). A, D, and E are the correct combination.

Why the Other Options Are Wrong

B adds a deploy stage with AWS CodeDeploy as the action provider. CodeDeploy requires additional artifacts and configuration, including an appspec.yml file, a deployment group, and a deployment configuration governing traffic shifting; none of that is needed to roll out a new ECS service revision, so using CodeDeploy adds management overhead that the requirement explicitly asks to avoid. jamesf identified the ECS action provider as the direct route that ensures the service is updated. C adds an appspec.yml file to the CodeCommit repository. appspec.yml is the artifact CodeDeploy reads for its lifecycle hooks and file mappings; because the deploy stage uses the ECS action provider rather than CodeDeploy, that file would never be consumed, so it is unused configuration. The omission of the imagedefinitions.json output, addressed by option D, would leave the ECS deploy action without the new image tag. A, D, and E are correct.

Community Comment Notes

Community voted A,D,E unanimously. xdkonorek2 cited the CodePipeline documentation page for an ECS continuous deployment pipeline, which matches the three steps. jamesf highlighted the keyword least management overhead and explained that configuring ECS as the action provider deploys the container image to ECS and ensures the service is updated. youonebe confirmed A,D,E without further qualification. No alternative received support.