AWS Builder Center
Weekend Creative Challenge: Driftnote

Weekend Creative Challenge: Driftnote

Cast three words into the tide and receive a found letter, poem, rumor, or lullaby. Driftnote is a serverless creative toy, API Gateway, Lambda, and Amazon Bedrock Nova Lite turn ordinary words into messages washed ashore.

Bridging Data and AI ✨


Vision & what the app does

Driftnote is a tiny creative app with one clear job: turn three ordinary words into something that feels washed ashore. You cast a trio of “tide-words” or hit Spin relics for surprises like lantern, mango, and compass then choose a form: letter, poem, rumor, or lullaby. A moment later, a bottle tumbles toward shore and opens into a found message from an invented coastal place and an invented sender.
The creative output is always short writing meant to make people smile. Each note arrives with a stamp (“Found near…”), a title, a signature, and a body that weaves your three words into the story instead of listing them like a checklist. It is not a productivity tool and not a chatbot. It is a toy: cast, wait, read, cast again.
I built Driftnote for the AWS Builder Center Weekend Creative Challenge because I wanted something playful that still shows real generative AI on AWS and a clean serverless path that fits Free Tier. In a world of dashboards and pipelines, a message in a bottle felt like the right kind of weekend project focused, delightful, and easy to demonstrate in screenshots or a live URL.
Try a combo if you want a reliable grin: thermos · sparrow · lighthouse as a rumor, or typewriter · honey · umbrella as a lullaby. Every cast is unique enough to share, short enough to read aloud, and concrete enough to feel handmade.


How you built it

I started from the challenge prompt “make something creative: words, images, sound, or play” and deliberately refused feature creep. A full story studio can become a product roadmap. A found-note toy stays honest: one input ritual, one creative artifact, one smile.
Key decisions shaped the build:
First, I chose words as the medium. Text generation is fast, cheap on Nova Lite, and perfect for proving creative output without wrestling image pipelines over a weekend.
Second, I avoided a blank chat box. Spinning relics and picking a form lowers blank-page fear and makes the interface feel like an interactive toy rather than a prompt console.
Third, I authenticated to Bedrock with a long-term Bedrock API key ( AWS_BEARER_TOKEN_BEDROCK ) The Bearer token path unblocked the demo immediately: Lambda calls the Converse API over HTTPS with  Authorization: Bearer … .
Fourth, I forced the model to answer in compact JSON:  title ,  from ,  place ,  body. So the UI can render a paper note, not a raw chat transcript. That schema decision did more for the product feel than any visual polish alone.
Fifth, I moved the API onto API Gateway + AWS Lambda. Each cast is a short, bursty request perfect for serverless. The React UI talks to  POST /api/drift ; API Gateway invokes the Lambda; the function returns the note. Locally, a tiny Express process emulates API Gateway and calls the same handler, so development stays fast without deploying on every save.
Challenges showed up early. Generic prompts produced generic prose; tightening the system instructions (concrete images, PG tone, weave words naturally, form-specific length) made results feel like objects found on a beach. Packaging shared TypeScript for Lambda with SAM’s esbuild metadata kept one source of truth for the Bedrock client. When generation failed, clear API errors (“the tide kept the note”) kept the metaphor intact instead of dumping stack traces on the user.
The stack stayed intentionally small: React + Vite for the coastal UI (hosted on S3 behind CloudFront), API Gateway + Lambda for  POST /api/drift , and Amazon Bedrock Nova Lite for the writing all described in  template.yaml  and deployed with  ./deploy_sam.sh .

AWS services used / architecture overview

Driftnote’s production architecture is fully serverless on the request path:
  1. Amazon S3 + Amazon CloudFront — static React UI
  1. Amazon API Gateway (HTTP API) — public routes  /api/drift  and  /api/health 
  1. AWS Lambda — runs the cast handler ( driftnote-cast )
  1. Amazon Bedrock (Nova Lite) —  amazon.nova-lite-v1:0  via the Converse API
Auth to Bedrock is the API key stored as a Lambda environment variable (SAM parameter  BedrockApiKey )
Architecture in one line:
React (CloudFront/S3) → API Gateway → Lambda → Bearer token → Bedrock Nova Lite → JSON note → paper-style UI.


What you learned

I learned that Bedrock long-term API keys are a practical unlock when IAM policies block  InvokeModel  but you still need a working generative demo. I learned that constraining the model to a tiny JSON schema makes frontend design dramatically easier than free-form chat. Moving the API to Lambda taught me that creative toys and serverless are a natural fit: you only pay when someone casts a note, and the same handler can run behind a local emulator during development.
Driftnote reminded me that creative software on AWS does not have to be large. It just has to wash something wonderful ashore.


Link to app or repo

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