Skip to content

Replace static AWS credentials with OIDC role assumption - #4

Open
psi wants to merge 1 commit into
masterfrom
oidc-app-workflows
Open

Replace static AWS credentials with OIDC role assumption#4
psi wants to merge 1 commit into
masterfrom
oidc-app-workflows

Conversation

@psi

@psi psi commented Aug 27, 2026

Copy link
Copy Markdown
Member

Summary

  • Replace static IAM credentials (TRUSS_AWS_ACCESS_KEY_ID / TRUSS_AWS_SECRET_ACCESS_KEY) with OIDC role assumption via aws-actions/configure-aws-credentials
  • Add permissions: id-token: write at the workflow level to enable OIDC token generation
  • Part of org-wide OIDC migration (PIER-821)

What changed

GitHub Actions workflows now authenticate to AWS using OpenID Connect (OIDC) instead of static IAM access keys. This:

  • Eliminates long-lived credentials stored as org secrets
  • Uses short-lived, automatically rotated tokens
  • Follows AWS and GitHub security best practices

Test plan

  • CI checks pass on this PR
  • Verify workflow runs succeed after merge (ECR push, deploys, etc.)

🤖 Generated with Claude Code

Migrate GitHub Actions workflows from static IAM credentials
(TRUSS_AWS_ACCESS_KEY_ID / TRUSS_AWS_SECRET_ACCESS_KEY) to OIDC
role assumption via aws-actions/configure-aws-credentials.

This is part of an org-wide migration to eliminate static AWS
credential usage in CI/CD pipelines (PIER-821).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant