AWS Builder Center

Weekend Annoying Task Challenges: Quick Notes App

Quick Notes App:A simple, lightweight notes app built entirely on Amazon S3 Static Website Hosting. Users can write a quick note, save it instantly, view all saved notes with timestamps, and delete the ones they don't need anymore, no login, no backend server, no complicated setup. Just open the link and start jotting things down. Built to solve the everyday problem of losing track of quick reminders and random thoughts scattered across different apps.

The Annoying Task

Like a lot of people, I kept jotting down reminders and quick notes in random places, WhatsApp messages to myself, sticky notes, half the time forgetting where I even wrote something down. I needed one simple, always-available place to save quick notes.

The Solution

For AWS's Weekend Challenge: "Turn One Annoying Task Into an App": I decided to keep it simple and build a Quick Notes App, hosted entirely on Amazon S3.

How I Built It

  1. Amazon S3 Bucket: Created a bucket and enabled Static Website Hosting, which lets S3 serve a website directly without needing a separate web server.
  1. Simple Frontend (HTML/CSS/JavaScript): Built a lightweight single-page app where I can type a note, save it, view all saved notes with timestamps, and delete ones I no longer need.
  1. Bucket Policy: Configured public read access so the site is accessible to anyone via the S3 website endpoint.
  1. Deployment: Uploaded the  index.html  file directly to the bucket. No servers, no complex backend: just S3 doing the heavy lifting.

Challenges I Faced

  • Started with Amazon Bedrock: My original plan was to use Amazon Bedrock (with Claude and Amazon Nova models) to build an AI-powered summarizer. However, since this was a brand-new AWS account, I kept hitting a ThrottlingException: "Too many tokens per day": even before making any real requests. This turned out to be a default low token quota that new AWS accounts get for Bedrock models, which resets after 24 hours or requires a quota increase request.
  • Anthropic use-case form: Before using Claude models, I also had to submit a one-time "use case details" form, since Anthropic requires this for first-time users on a new account.
  • Pivoted the idea: Rather than wait 24 hours for the quota to reset, I decided to keep the challenge spirit alive and pivot to a simpler, guaranteed-to-work idea using Amazon S3 Static Website Hosting instead: which turned out to be a great lesson in staying flexible when cloud services hit account-level limits.
  • S3 permissions: Initially the site wasn't loading because of the default "Block all public access" setting on the bucket. Had to uncheck that and add a public-read bucket policy before the static website endpoint worked.

What I Learned

  • How fast you can go from idea to a live, working app using just S3's static website hosting feature.
  • The importance of getting bucket permissions and policies right for public access.
  • Even a small, "boring" annoying task can turn into a genuinely useful mini-project.

Result

A simple, working notes app, live and hosted on AWS, solving a real everyday annoyance in under an hour.
AWS Services Used: Amazon S3 (Static Website Hosting)
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