← All insightsCI/CD

Integrating Amazon Web Services into your CI/CD pipeline

Nir Geier, CodeWizard · 17 January 2026 · 3 min read · Intermediate

Getting Amazon Web Services into your pipeline is where it starts paying off - automated, repeatable and reviewed. Here is a working integration and the habits that keep it reliable.

A working pipeline snippet

Authenticate from CI with OIDC, not stored keys.

yaml
permissions: { id-token: write, contents: read }
steps:
  - uses: aws-actions/configure-aws-credentials@v4
    with:
      role-to-assume: arn:aws:iam::1234:role/ci
      aws-region: eu-west-1

Do this

  • Use SSO for humans and OIDC roles for CI - no static keys
  • Write least-privilege IAM and manage everything via IaC
  • Turn on CloudTrail, GuardDuty and budget alerts

Avoid this

  • Long-lived access keys instead of SSO/OIDC roles
  • Over-broad IAM policies with wildcard actions and resources
  • Public S3 buckets and security groups open to 0.0.0.0/0

Want senior help putting Amazon Web Services to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult