Course contentsShow
← Cloud and Infrastructure
Lesson 1847 of 2,98938. AWS Native CI/CDFree lesson

Pipeline Artifacts and Artifact Stores

Managing input and output artifacts, configuring S3 artifact stores, and artifact encryption.

Pipeline Artifacts and Artifact Stores

You'll learn: How CodePipeline manages artifacts between stages using encrypted S3 buckets.

What Are Pipeline Artifacts?

In CodePipeline, artifacts are the files or data that move between stages—like compiled code, configuration files, or build outputs. When your source stage pulls code from CodeCommit, it creates an artifact. When CodeBuild compiles that code, it outputs another artifact. Each stage can consume artifacts from previous stages and produce new ones.

Think of artifacts like relay batons in a race: each runner (stage) receives the baton from the previous runner and passes a potentially modified version to the next.

Artifact Stores: The S3 Backend

CodePipeline requires an artifact store—an S3 bucket—to temporarily hold these artifacts between stages. When you create a pipeline, AWS automatically creates or lets you specify an S3 bucket for this purpose.

Key characteristics:

  • Regional: Each pipeline region needs its own artifact store
  • Cross-region pipelines: Require one artifact store per region involved
  • Automatic encryption: Artifacts are encrypted at rest using AWS KMS keys (either AWS-managed or customer-managed)

Managing Artifacts

You control what gets passed between stages through your buildspec or appspec configurations. For example, CodeBuild's artifacts section defines which files become the output artifact. The pipeline automatically handles upload/download to/from S3—you don't manually interact with the bucket.

Encryption: By default, AWS encrypts artifacts with an AWS-managed key. For compliance requirements, you can specify a customer-managed KMS key, ensuring only authorized services and users can decrypt pipeline data.

Key Takeaway: CodePipeline artifacts are the connective tissue between stages, automatically stored in encrypted S3 buckets that act as secure handoff points throughout your CI/CD workflow.