AWS Builder Center
Turning 'I Keep Forgetting My Habits' Into a Real Serverless App — Meet StreakUp, My AWS Weekend Challenge Build

Turning 'I Keep Forgetting My Habits' Into a Real Serverless App — Meet StreakUp, My AWS Weekend Challenge Build

StreakUp : A serverless Habit Tracker built for AWS's Weekend Challenge. Add daily habits, mark them done, and watch your streak grow, all powered by Amazon S3, API Gateway, Lambda, and DynamoDB. No servers, just clean cloud architecture solving a real everyday problem: staying consistent with habits.

Turning "I Keep Forgetting My Habits" Into a Real Serverless App — Meet StreakUp, My AWS Weekend Challenge Build

The Annoying Task

Building good daily habits, drinking enough water, exercising, studying consistently, is hard enough on its own. What made it worse for me was having no simple way to track whether I actually did them each day, or how long my streak had lasted. Sticky notes and phone reminders never stuck around long enough to matter.
So for AWS's Weekend Challenge, "Turn One Annoying Task Into an App," I decided to build StreakUp, a Habit Tracker backed by a real serverless architecture on AWS.

What I Built: StreakUp

A simple web app where you can:
  • Add a daily habit you want to build
  • Mark it done for the day with one click
  • Automatically track a streak counter (consecutive days completed)
  • Delete habits you no longer need
  • Come back anytime, on any device, and see your data still there (because it's stored in the cloud, not just the browser)

Architecture

Instead of keeping things purely static, I wanted this to be a genuine full-stack serverless app, so I used four AWS services together:
  1. Amazon S3 – Hosts the frontend as a static website (HTML, CSS, JavaScript). No web server needed.
  1. Amazon API Gateway – Exposes a REST API ( GET ,  POST ,  PUT ,  DELETE  on  /habits ) that the frontend calls to talk to the backend.
  1. AWS Lambda – Runs the backend logic in Python: adding habits, toggling them done/undone, calculating streaks, and deleting them. No servers to manage, it only runs when called.
  1. Amazon DynamoDB – A NoSQL database table ( HabitsTable ) that permanently stores every habit and its streak count.
Flow: User opens the S3-hosted page → clicks a habit as done → the page calls the API Gateway endpoint → API Gateway triggers the Lambda function → Lambda reads/writes to DynamoDB → the updated data is sent back and rendered on the page.

Challenges I Faced

  • IAM permissions: The Lambda function initially couldn't read or write to DynamoDB until I attached the  AmazonDynamoDBFullAccess  policy to its execution role.
  • CORS errors: Since the frontend (S3) and backend (API Gateway) live on different origins, I had to enable CORS on every method ( GET ,  POST ,  PUT ,  DELETE ) so the browser wouldn't block the requests.
  • S3 public access: Had to disable "Block all public access" and add a bucket policy before the static website was reachable.
  • Deploying the API: Learned the hard way that creating methods in API Gateway isn't enough, you have to explicitly Deploy API to a stage (like  prod ) before the endpoint actually goes live.

What I Learned

  • How to wire together a real serverless backend: S3 → API Gateway → Lambda → DynamoDB, entirely without managing a server.
  • The importance of IAM roles and permissions in letting AWS services talk to each other securely.
  • CORS is one of the most common (and most confusing) issues when connecting a static frontend to an API, understanding it properly saved a lot of debugging time.
  • Even a small personal annoyance, forgetting to track habits, can become a solid, portfolio-worthy cloud project.

Result

A live, cloud-hosted Habit Tracker app called StreakUp, where my data persists in a real database, accessible from anywhere, built entirely on AWS serverless services.
AWS Services Used: Amazon S3, Amazon API Gateway, AWS Lambda, Amazon DynamoDB
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