AWS Builder Center
Weekend Annoying Task Challenge: Inficsion

Weekend Annoying Task Challenge: Inficsion

Read it !!

Student Builder Campus Leader

Weekend Annoying Task Challenge: Weekly Status Update Drafter

Vision & What the App Does
Okay so here's my annoying task: every single week I have to write a status update for my team, and every single week I stare at a blank email for way longer than I should. I know what I did. I just can't turn it into something that sounds put-together in under two minutes. It always turns into 20-30 minutes of "wait how do I phrase this."
So I built the Weekly Status Update Drafter. You dump in your rough, messy notes — "finished the Q3 report, fixed 3 bugs, met with client on Tuesday" — and it spits back a clean, formatted email draft you can just send. That's it. No login, no fluff, just paste and go.
The goal wasn't to build something fancy. It was to kill the one tiny task that eats my Friday afternoons.

How You Built It

I gave myself a pretty simple flow on paper before touching any AWS console: a text box, a button, and something on the backend that takes the notes and turns them into a formatted draft. Frontend → API → function → response back to the browser.
Honestly the build itself was straightforward, but I hit a wall I wasn't expecting: CORS. My first few requests from the frontend just silently failed — no error message that actually told me what was wrong, just a vague cross-origin complaint in the browser console. Turns out you have to fix it in two places, not one — both the API Gateway CORS settings and the headers you return from Lambda itself. I only figured that out after a few frustrating rounds of "why is this still not working."
I went with an HTTP API in API Gateway instead of a REST API since I didn't need any of the heavier request/response transformation stuff — just a simple POST endpoint. And for the actual drafting logic, I kept things lightweight in Lambda: parse the notes, structure them into a clean email format, done. Given I was building under a real time crunch, keeping it simple was less "design choice" and more "this is what actually gets shipped today."

AWS Services Used / Architecture Overview

Services used:
  • Amazon S3 — hosts the frontend as a static website (just one HTML page)
  • Amazon API Gateway (HTTP API) — exposes a POST  /draft  endpoint the frontend calls
  • AWS Lambda — Python function that takes the raw notes and formats them into the draft
How it's wired together:
Browser (S3 static site)
|
v
API Gateway → POST /draft
|
v
Lambda (Python)
|
v
Formatted draft sent back to the browser
It's triggered on-demand — you click the button, that fires an HTTP request through API Gateway, which calls Lambda synchronously. Lambda formats the notes into the email structure and hands the response straight back. No queues, no background jobs, nothing async. Click it, and a second later you've got your draft.

What You Learned

Honestly, the biggest thing I walked away with is how little you actually need to ship something useful. Three services, each doing one job, no servers to babysit.
The CORS debugging was a good reminder too — when something fails silently in the browser, don't assume it's just one setting. Check both sides of the connection before you start second-guessing your whole architecture.
And building this under a genuine deadline crunch taught me to just... not gold-plate it. I wanted to add more features, more polish, but I forced myself to get one clean flow working end-to-end first. Turns out that's usually the right call anyway — simpler ended up being more reliable.

Link to App

Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article