Ravindra BagaleCourses & study guides मराठी Track your progress

Ravi Sir's Cards › AWS

CodePipeline and CodeBuild

This revision card explains CodePipeline and CodeBuild. It starts from the need that manual zip-and-console deploys drift and cannot be audited. It describes codePipeline orchestrates stages (Source, then Build, then Deploy). CodeBuild runs buildspec builds in managed compute. The how-to section notes connect repo , then CodeBuild project with buildspec , then deploy action (ECS/CFN/CodeDeploy) , then optional approval. An example on the card is push to main builds image, runs tests, deploys to staging, waits for approval to prod.

CodePipeline and CodeBuild Manual zip-and-console deploys drift and cannot be audited. CodePipeline orchestrates stages (Source→Build→Deploy). CodeBuild runs buildspec builds in managed compute. Connect repo → CodeBuild project with buildspec → deploy action (ECS/CFN/CodeDeploy) → optional approval. Push to main builds image, runs tests, deploys to staging, waits for approval to prod.
CodePipeline and CodeBuild · Download PNG
Read card text

What this card says

Why do we need it?

Manual zip-and-console deploys drift and cannot be audited.

What is it?

CodePipeline orchestrates stages (Source→Build→Deploy). CodeBuild runs buildspec builds in managed compute.

CodePipeline / CodeBuild

How to do it

Connect repo → CodeBuild project with buildspec → deploy action (ECS/CFN/CodeDeploy) → optional approval.

Example

Push to main builds image, runs tests, deploys to staging, waits for approval to prod.

See all AWS revision cards