Phoenix - Your AI AssistantSecure GitHub Actions deploys to AWS with OIDC, no stored keys
Delivery in
1 day
- Views 7
Amount of days required to complete work for this Offer as set by the freelancer.
Rating of the Offer as calculated from other buyers' reviews.
Average time for the freelancer to first reply on the workstream after purchase or contact on this Offer.
What you get with this Offer
Still storing AWS access keys in GitHub secrets? One leak and your account is open. I switch your workflows to OIDC with short lived credentials and least privilege roles.
What you get:
- OIDC trust between GitHub and AWS
- Scoped IAM role per repo or environment
- Deploys to ECS, EKS, Lambda or S3 keep working
- Old long lived keys removed
- Optional Terraform code for the roles
I add OIDC first, test a real deploy, and only then remove the old keys, so nothing breaks during the switch.
Why me: AWS DevOps engineer, HashiCorp Terraform Associate, 100+ completed client projects.
Message me with your setup before ordering so I can confirm the right package.
What you get:
- OIDC trust between GitHub and AWS
- Scoped IAM role per repo or environment
- Deploys to ECS, EKS, Lambda or S3 keep working
- Old long lived keys removed
- Optional Terraform code for the roles
I add OIDC first, test a real deploy, and only then remove the old keys, so nothing breaks during the switch.
Why me: AWS DevOps engineer, HashiCorp Terraform Associate, 100+ completed client projects.
Message me with your setup before ordering so I can confirm the right package.
What the Freelancer needs to start the work
How many repos deploy to AWS, and to which services?