Migrating from IAM Secret and Access Keys to OIDC for Secure AWS Deployments
Changing our GitHub Action to leverage OIDC instead of hard-coded AWS Secret and Access Keys.
Changing our GitHub Action to leverage OIDC instead of hard-coded AWS Secret and Access Keys.
In this tutorial, we will configure a static website using Jekyll, GitHub Actions, AWS S3, AWS Route 53, AWS Certificate Manager, AWS CloudFront, and AWS CloudFormation. And yes, that sounds like a mouthful, but trust me, it’s not as intimidating as it sounds. To begin, we’ll highlight the main technologies being used and the role they play in our solution. Next, I’ll dive into the roles of each AWS offering used in this architecture, including how CloudFormation is used to create and manage the infrastructure for our website, how Route 53 and Certificate Manager are used to manage our domain, DNS records, and TLS certificates, and how CloudFront will be used for content delivery and caching. ...