Back to Knowledge

Building with AWS

Already invested in the AWS ecosystem? Here's how to build modern web apps using Amazon's cloud services - and when it makes sense over simpler alternatives.

1AWS vs Vibe Stack: When to Choose What

AWS is incredibly powerful, but it's also complex. Here's the honest comparison to help you decide.

Choose AWS If...

  • Your company already uses AWS
  • You need complex infrastructure (VPCs, custom networking)
  • You want complete control over every detail
  • Your team has AWS expertise
  • You need enterprise compliance features
  • You're building microservices at scale

Choose Vibe Stack If...

  • You want to ship fast with minimal config
  • You're building a web app or API
  • You want predictable pricing
  • You're a solo developer or small team
  • You value simplicity over flexibility
  • You don't have DevOps expertise

Our take: AWS gives you a massive toolbox - but you need to know which tools to use. The Vibe Stack (Vercel + Neon) is like having a smart assistant who picks the right tools for you. Both are valid; it depends on your needs and experience level.

2Recommended AWS Stack for Web Apps

AWS Amplify (Frontend Hosting)

Deploy React, Next.js, Vue apps with CI/CD built-in

Why Use It

  • • Git-based deployments (like Vercel)
  • • Preview deployments for PRs
  • • Built-in CDN with CloudFront
  • • Custom domains with SSL
  • • Integrates with AWS services

Gotchas

  • • Build times can be slow
  • • Less polished than Vercel/Netlify
  • • Configuration can be complex
  • • Limited framework optimizations

Comparable to: Vercel, Netlify - but with tighter AWS integration

AWS RDS (Database)

Managed PostgreSQL, MySQL, or other relational databases

Why Use It

  • • Automatic backups and point-in-time recovery
  • • Multi-AZ high availability
  • • Read replicas for scaling
  • • Automatic OS/database patching
  • • VPC isolation for security

Gotchas

  • • Always running = always paying ($15-100+/month)
  • • No free tier for production databases
  • • Requires VPC configuration
  • • Connection pooling not built-in

Comparable to: Neon, Supabase - but no scale-to-zero or branching features

AWS Lambda (Backend/API)

Serverless functions that run on demand

Why Use It

  • • Pay only for execution time
  • • Auto-scales to zero and infinity
  • • Event-driven architecture
  • • Integrates with all AWS services
  • • No server management

Gotchas

  • • Cold starts (300ms-3s delay)
  • • 15-minute execution time limit
  • • API Gateway adds complexity
  • • Local testing is harder

Comparable to: Vercel Serverless Functions, Cloudflare Workers - but more powerful and complex

AWS Cognito (Authentication)

User authentication and authorization service

Why Use It

  • • User pools with sign-up/sign-in
  • • OAuth 2.0 and social logins
  • • MFA and security features
  • • JWT tokens for authorization
  • • Scales to millions of users

Gotchas

  • • Complex setup with IAM roles
  • • UI customization is limited
  • • Can't export user passwords
  • • Pricing can add up at scale

Comparable to: Clerk, Auth0, Supabase Auth - but with deeper AWS integration

3Cost Breakdown & Free Tier

AWS pricing is pay-as-you-go, which sounds great until you realize how many services you need.

AWS Amplify

Frontend hosting + build minutes

$0-20/mo

1000 build minutes free

AWS RDS (db.t3.micro)

PostgreSQL or MySQL

~$15-25/mo

Always running, no scale-to-zero

AWS Lambda + API Gateway

Serverless functions + HTTP APIs

$0-10/mo

1M requests free/month

AWS Cognito

User authentication

$0-5/mo

50k MAU free tier

Monthly Total (Small App)

Low traffic, single region

~$20-60/mo

Database is the biggest cost

Vibe Stack (Comparison)

Vercel + Neon

$0-20/mo

Scale-to-zero = lower cost

Watch out for: Data transfer costs, NAT Gateway fees ($32/mo), CloudWatch logs, and multi-AZ database deployments can quickly add up. AWS bills can surprise you if you're not monitoring closely.

4Building AWS Apps with AI

Claude Code (Recommended)

Claude Code works great with AWS! It understands AWS SDK, CloudFormation, CDK, and can help you navigate the complexity.

Tip: When asking Claude to build AWS features, be specific about which services you want. AWS has 200+ services - clarity helps!

Amazon Q (AWS's AI Assistant)

Amazon's AI coding assistant designed specifically for AWS. Deep integration with AWS services and documentation.

• Knows AWS best practices

• Can generate CloudFormation/CDK code

• Integrated in AWS Console

• Understanding of AWS-specific patterns

Other AI Tools

ChatGPT, GitHub Copilot, and Gemini all understand AWS - but they might not have the latest service updates or deep AWS patterns. Claude and Amazon Q tend to be more reliable for AWS-specific code.

5Quick Start: Deploy to AWS Amplify

1

Create AWS Account

Sign up at aws.amazon.com. You'll need a credit card, but many services have free tiers.

2

Push Your App to GitHub

Amplify deploys from Git repositories. Make sure your Next.js/React app is in GitHub, GitLab, or Bitbucket.

3

Open AWS Amplify Console

Search for "Amplify" in the AWS Console. Click "Host web app" and connect your Git provider.

4

Select Your Repository

Choose the repo and branch. Amplify auto-detects Next.js, React, Vue, and other frameworks.

5

Configure Build Settings

Amplify generates build settings automatically. Add environment variables if needed.

6

Deploy

Click "Save and deploy". Amplify builds and deploys your app. Future Git pushes trigger automatic deployments.

Success! Your app is live on a .amplifyapp.com domain. You can add a custom domain in the Amplify settings.

6Common AWS Gotchas

IAM Permissions Hell

AWS uses IAM (Identity and Access Management) for permissions. It's powerful but confusing. You'll spend time debugging "Access Denied" errors.

Fix: Use AWS-managed policies when possible. Start permissive, lock down later. Use CloudWatch logs to debug permission errors.

VPC Networking Complexity

RDS databases live in a VPC (Virtual Private Cloud). Lambda functions need VPC configuration to access RDS, which adds complexity and cold start latency.

Fix: Use RDS Proxy or consider Aurora Serverless v2. Or skip the VPC pain and use Neon/Supabase instead.

Lambda Cold Starts

Lambda functions that haven't been called recently take 300ms-3s to "wake up". This can make APIs feel slow.

Fix: Use Provisioned Concurrency (costs money) or accept cold starts as part of serverless trade-offs. Or use Vercel Edge Functions for faster starts.

Surprise Bills

AWS pricing is complex. NAT Gateways ($32/mo), data transfer, CloudWatch logs, and API Gateway costs add up quickly.

Fix: Set up billing alerts immediately! Use AWS Cost Explorer. Delete unused resources. Consider using AWS Budgets to cap spending.

Ready to build on AWS?

AWS is powerful - just make sure it's the right fit for your project.

AWS Amplify Docs Back to Knowledge