AWS Builder Center

5 Intermediate AWS Projects to Build After Your First Deployment

Once you've deployed your first AWS projects, it's time to connect multiple services into real pipelines. This post walks through five intermediate builds — from a serverless URL shortener to an event-driven notification system — each doable in a weekend.

Last week we covered five beginner projects to get something live on AWS. If you've already knocked those out, it's time to combine services and start thinking about how real systems are actually built — not just single Lambda functions or static sites, but small pipelines that talk to each other. Here are five intermediate projects to build this weekend.

1. Build a URL Shortener with API Gateway + Lambda + DynamoDB

Take the "like counter" idea from last week further: build a full URL shortener where users submit a long URL, get back a short code, and hitting that code redirects them. Add a simple analytics counter (clicks per link) while you're at it. Skills you'll learn: REST API design, DynamoDB single-table design, Lambda routing logic

2. Set Up a CI/CD Pipeline with CodePipeline + CodeBuild

Instead of manually uploading your S3 site or redeploying Lambda code by hand, connect your GitHub repo to CodePipeline so every push automatically builds and deploys your app. Skills you'll learn: CI/CD concepts, CodeBuild buildspecs, IAM roles for automation

3. Build a Serverless Contact Form with SES

Add a real contact form to your portfolio site from Week 1. Use API Gateway + Lambda to receive form submissions and Amazon SES to send you an email notification, with basic spam protection (rate limiting or a honeypot field). Skills you'll learn: SES email sending, input validation, API throttling

4. Containerize an App with ECS Fargate

Take that Elastic Beanstalk to-do app from last week and redeploy it as a Docker container running on ECS Fargate instead. You'll deal with task definitions and services instead of EC2 instances directly. Skills you'll learn: Docker basics, ECS task definitions, Fargate networking

5. Build an Event-Driven Notification System with SNS + SQS

Simulate a real backend workflow: an event (like a new sign-up) publishes to an SNS topic, which fans out to multiple SQS queues — one for sending a welcome email, another for logging analytics. This is the pattern behind most production microservices. Skills you'll learn: Pub/sub architecture, SNS fan-out, SQS queues, decoupled services

A Few Tips Before You Start

  • Set up cost allocation tags by project name now — with more moving pieces, it's easy to lose track of what's costing you money.
  • Use a separate IAM user or role per project, not your root account, to start building good security habits early.
  • Diagram it first. Before writing code, sketch how the services connect — it'll save you debugging time and makes a great addition to your portfolio README.
  • Compare this week to last week. Write a short note on what changed architecturally — this reflection is what actually shows growth to anyone reviewing your work.
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