Deploying Multi-Cloud Resume to GCP: Frontend and Backend
This post details the deployment of our multi-cloud resume to GCP. The frontend is deployed to Cloud Storage and Cloud CDN, while the backend is deployed to Cloud Functions and Firestore.
This post details the deployment of our multi-cloud resume to GCP. The frontend is deployed to Cloud Storage and Cloud CDN, while the backend is deployed to Cloud Functions and Firestore.
I wanted to automate deployments using GitHub Actions instead of running manual scripts. OIDC authentication eliminates the need to store AWS credentials in GitHub secrets while providing secure, temporary access tokens. While this is more complex than manual scripts, it mirrors the constraints of production CI/CD environments.
I was building my AWS infrastructure with Terraform, running terraform apply from my laptop, when I hit a wall planning CI/CD. My Terraform state file was local - sitting in my project directory. That doesn't work for automated deployments.
Today I built the complete infrastructure for hosting a static website on AWS using Terraform. This covers S3 storage, CloudFront CDN, SSL certificates, and DNS configuration.