Question 1

What's the difference between CodeBuild and CodePipeline?

Accepted Answer

CodeBuild runs the build steps: compiling code, running tests, and creating artifacts (like a ZIP, JAR, or container image). CodePipeline orchestrates the whole workflow across stages (source, build, test, deploy) and connects services together. In many setups, CodePipeline triggers CodeBuild as the build stage.

Question 2

When should I use CodeBuild?

Accepted Answer

Use CodeBuild when you want a managed, scalable way to run builds and tests without maintaining your own build servers. It’s a good fit if you need builds triggered by commits or pull requests, want consistent build environments, need parallel builds for multiple projects, or want to produce artifacts for deployment (for example, a packaged app or a container image).

Question 3

How much does CodeBuild cost?

Accepted Answer

CodeBuild pricing is primarily based on build minutes and the compute type you choose (for example, smaller vs. larger build environments). Your total cost depends on how often builds run, how long they take, whether you run builds in parallel, and any additional costs for related services (such as storing artifacts in S3, pulling images from ECR, or logging to CloudWatch). Always check the current AWS CodeBuild pricing page for exact rates by region and compute type.

CodeBuild

Definition

Real-World Example

Related Terms

Cloud Provider Equivalencies

Explore More Cloud Computing Terms