GitHub Actions deploy uses long-lived AWS keys
OIDC trust lets GitHub Actions assumeRole without repo secrets. Switch over.
Try this first
- 1Create an IAM OIDC provider for token.actions.githubusercontent.com
- 2Create a role with trust policy scoped to your org/repo and environment
- 3Workflow uses aws-actions/configure-aws-credentials with role-to-assume
- 4Delete the old AKIA keys from repo secrets
When to bring us in
Azure and GCP have similar OIDC setups (Federated Identity Credentials, Workload Identity Federation).
See also
- Everyone logs in with the AWS root accountRoot is for emergencies and billing. Day-to-day work belongs in IAM users or SSO.
- Every developer has AdministratorAccessAdministratorAccess everywhere is convenient now, painful later. Start with role-based policies.
- Everyone has individual IAM users with their own passwordIdentity Center (formerly AWS SSO) links to your IdP and issues temporary credentials per session.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.