The latest articles on DEV Community by Richard Babatola (@babatolaor8433). https://dev.to/babatolaor8433 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4209814%2F95f31635-1de9-43bf-b35a-1816d0a8e5bf.png https://dev.to/babatolaor8433 en Richard Babatola Tue, 27 Oct 2026 03:27:57 +0000 https://dev.to/babatolaor8433/what-i-learned-building-this-resume-on-aws-2p4n https://dev.to/babatolaor8433/what-i-learned-building-this-resume-on-aws-2p4n <p>I built my resume as a static site and put a visitor counter behind it. The page is one HTML file. The number on the page is a small serverless API.</p> <p>Amazon S3 stores the file in a private bucket. CloudFront is the public address, and it is the only thing allowed to read the bucket. A visitor who opens the S3 URL directly is denied. HTTPS is the CloudFront certificate. I kept that hostname instead of attaching a domain I already owned.</p> <p>The browser does not talk to DynamoDB. The page calls an HTTP API, API Gateway invokes a Python Lambda function, and the function adds 1 to one row in a DynamoDB table. The table key is a string, <code>Id_string</code>, and the row id is <code>resume</code>. The JavaScript looks up an element with <code>id="visitor-count"</code> and writes the number there. A script with no matching element calls the API and shows nothing.</p> <p>I created the table, the function, and the API in the console first. Terraform came second. <code>terraform import</code> told Terraform that those resources already existed, so apply updated the function code instead of creating a second copy. The state file lives in a private S3 bucket. GitHub Actions cannot see a state file that exists only on my laptop.</p> <p>The Python test never calls AWS. It replaces the DynamoDB table with a fake and checks that the function asks for an increment of 1 and returns that count. The first GitHub Actions run still failed. Importing the function creates a DynamoDB resource immediately, and the runner had no AWS region, so pytest failed before the fake was in place. Setting a region in the test fixed the import. The test still does not increment the live count.</p> <p>Two repositories deploy two different things. A push to the API repository runs the test and then <code>terraform apply</code>. A push to the website repository uploads <code>index.html</code> and invalidates the CloudFront cache. The AWS keys for those workflows are GitHub secrets. They are not in the repository.</p> aws terraform serverless Richard Babatola Tue, 27 Oct 2026 03:16:00 +0000 https://dev.to/babatolaor8433/-title-what-i-learned-building-this-resume-on-aws-published-true-tags-aws-terraform-2lmc https://dev.to/babatolaor8433/-title-what-i-learned-building-this-resume-on-aws-published-true-tags-aws-terraform-2lmc aws serverless webdev