Day 12: AWS Cloud Resume Challenge

Today was the day it all came together. I had the database, the logic, and the API ready—I just needed to write the code that would actually "place the order" from my website.

The Frontend Fetch

I spent today working in JavaScript, using the fetch() API. It’s a relatively simple block of code, but it does a lot of heavy lifting. It reaches out to my API Gateway URL, waits for the response, and then tells my HTML: "Hey, take this number and put it in that specific spot on the page."

The Deployment "Gotcha"

After I updated my code and uploaded it to S3, I refreshed my site and... nothing changed.

This was a great lesson in CDN Caching. Because my site sits behind CloudFront, the old version of my JavaScript was still saved in the "edge" locations. I had to run a CloudFront Invalidation (/*) to force AWS to dump the old cache and grab my brand-new code from S3.

Proof of Life

Once the invalidation finished, I refreshed the page and saw it: "You are visitor number: 1".

It’s just a small number on a screen, but knowing that number travelled from my browser, through a secure API, triggered a Python script, updated a NoSQL database, and came all the way back is an incredible feeling.

Up Next

The backend is bulletproof, but the UI is currently just plain black text. Now that the logic is working, I’m going to focus on the "Design" phase—using CSS to make this counter look like a professional, integrated part of my resume rather than an afterthought.

#CloudResumeChallenge #FullStack #AWS #JavaScript #S3 #CloudFront #Serverless #Day12BuildInPublic