AWS offers at least four ways to host a SaaS, from near-effortless to full-control. Here are the four paths, what they cost in time and money, and how to choose based on your team.
Julien Mauclair · ~9 min · intermediate
StackAmplifyEC2ECSLambdaRDSS3
01The four paths
From most managed to most manual. The further down, the more you control — and the more you manage.
Amplifythe “Vercel of AWS”: push, build, deploy. The simplest.
Lambdaserverless: API + static front, pay per use.
ECS/Fargateyour container, no machine to manage. The sweet spot.
EC2a machine of your own. Full control, floor cost at stable load.
02How to choose
Solo / MVP
Amplify or Lambda: the least infra possible, you stay on the product.
Small team
ECS/Fargate: clean containers, managed scale, no sysadmin.
Control needed
EC2: legacy PHP, GPU, precise config, or floor cost at constant load.
Common to all
RDS for the database, S3 for files. That doesn’t change with the compute.
Whatever the compute, the data architecture is the same: managed database on RDS (never on the compute’s disk), files and media on S3 served by CloudFront. That decoupling is what makes the whole thing robust and scalable.
AWS is more verbose than Vercel, but often cheaper at scale — provided you watch it. The classic trap: underestimating peripheral costs (data transfer, NAT, snapshots).
AWS doesn't force a choice between simplicity and control: Amplify to start, ECS when it grows, EC2 when you want to own everything — always with RDS and S3 as the foundation. Choose for your team today, not for the scale you hope for.
Julien MauclairJulien Mauclair is the co-founder and CTO of Klickbee, where he builds the agency’s websites, tracking and AI automations, and develops Klickbee Tracking. He also runs Stralya, which designs and runs AWS infrastructure for scale-ups. Before that, he built the entire AWS infrastructure of an e-commerce business, since sold.