AWS Builder Center

Weekend Showcase Challenge: Nook

A cozy serverless study corner on Amazon S3, Lambda, and Amazon Bedrock that turns dense notes into a plain-English explanation plus flip-card quizzes — with a resilient offline fallback. My first summer build.

Computer Science Student · AWS Student Builder Campus Leader · Cloud & Generative AI
For most of the summer, highlighters were the master of my study routine — and rereading never actually proved I understood anything. It made my notes familiar, not clear. So I built Nook: a cozy, serverless corner that turns dense notes into a plain-English explanation plus flip-card quiz questions you can actually test yourself on.

Vision and what it does

Nook solves the "I highlighted this, but I can't explain it" problem. You paste a messy paragraph, a lecture summary, or a single question, and within seconds you get two things: a bulleted, plain-English explanation of every key idea in your notes, and three multiple-choice flip-cards with the correct answer hidden until you flip each one. It's built around how I actually study: read it plainly, then prove it to yourself.

How I built it

The frontend is a single static page (HTML/CSS/JS) with a cozy, library-like theme — cream paper, serif type, a little lamp logo — hosted on Amazon S3 static website hosting. It calls one Python (3.13) Lambda function directly through a Lambda Function URL, so there's no API Gateway, no server, and nothing to babysit. Both pieces sit comfortably inside the $200 in Free Tier credits AWS gives new accounts.
The Lambda is Bedrock-first: it asks Amazon Nova Lite for a strict JSON object (explanation plus three questions with distractors and answers) and renders it. Then came the challenge that taught me the most this summer. My very first invocation failed with "Operation not allowed ... forbidden by your account's security policy." My IAM policy and model access were correct, yet every model in every region refused — a new-account restriction that only AWS Support can lift. I opened a support case under the Bedrock Allowlisting category, so it will be enabled within days.
Instead of shipping a broken app, I shipped a resilient one. The Lambda detects account-blocked errors and falls back to a local engine that builds the same study sheet from the notes: it splits them into statements, rewrites each in plain language, and generates real quiz options drawn from the text itself. The UI shows a small note so it's transparent, and the moment Bedrock goes live every request routes to Nova Lite automatically. One function, two paths, no downtime.
Smaller wins along the way: scoping the Function URL's CORS allowed origin to exactly my S3 site, wrestling PowerShell's BOM bytes out of the Lambda zip, and learning to read error messages before touching IAM.

AWS services used and architecture overview

  • Amazon S3 — static website hosting and the public-read bucket policy for the frontend.
  • AWS Lambda (Python 3.13) — the entire backend, exposed directly via a Lambda Function URL.
  • Amazon Bedrock (Nova Lite) — the primary generator, called through boto3.
  • IAM — a least-privilege execution role allowing only bedrock:InvokeModel on the Nova Lite model ARN.
Browser → S3 static site → Lambda Function URL → Python handler → Amazon Bedrock (Nova Lite) or the built-in offline fallback → plain-English explanation plus three flip-cards.

What I learned across the summer

This was my first serious AWS build, and I learned to tell the difference between an IAM problem, a boto3 problem, and an account-level problem — they feel identical and they are not. I picked up least-privilege IAM, Function URLs and CORS, S3 hosting and bucket policies, and the discipline every strong build shares: work around real constraints instead of ideal assumptions. And the biggest lesson of the summer — you don't need to know everything before you start. You need a working link by Sunday.
#AWSBuilder #AmazonBedrock #AWSLambda #AmazonS3 #Serverless #GenerativeAI
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