Developer Builds Terraform and GitHub Actions Pipeline for Cloud Resume Challenge

A developer completed the third week of the Cloud Resume Challenge by replacing manual AWS Console workflows with Infrastructure as Code using Terraform. All AWS resources — including an S3 bucket, DynamoDB table, Lambda function, and API Gateway — were defined in Terraform configuration files. A remote S3 backend was set up to store Terraform state, ensuring both local development and GitHub Actions CI/CD pipelines share a consistent view of infrastructure. The developer chose Terraform over the recommended AWS SAM due to its cloud-agnostic nature and high industry demand. Key bugs encountered included resource conflict errors from pre-existing manually created resources, which were resolved by importing them into Terraform state.