I stopped putting AWS keys in GitHub Secrets. Here's what I do instead.

For a while my deploy pipelines all worked the same way. Generate an IAM user, copy its access key and secret into GitHub repo secrets, and let the workflow use them. It deploys fine. It also means a long-lived credential to my AWS account is sitting in a third party's vault, valid until I remember

Related Stories

📰

Accelerate your infrastructure deployments by up to 4x with AWS CloudFormation Express mode

What 12 failure classes and 30 Billion tokens spent taught us about trusting AI coding agents

📰

Tech Crush Assignment 5

📰

Convergence of Calendars: Arabic Date Converter's Hidden Tech Secrets