AWS Amplify limitations
AWS Amplify promises easy serverless deployment, but its limitations can block you from running modern, complex apps—especially Next.js. Here's what you need to know before committing.
What is AWS Amplify?
Amplify is AWS's serverless platform for deploying web apps. You don't manage infrastructure directly—AWS handles scaling, and you pay based on usage. For simple apps with low traffic, costs can be minimal.
But "serverless" comes with trade-offs that matter as your app grows.
Key limitations
Next.js support gaps
- No streaming support — React Server Components with streaming won't work
- Image size limit (4.3 MB) — Images processed with
next/imagemust be under this limit - Backend code limit (250 MB) — AWS Lambda's package size restriction applies
- Cold starts — Serverless functions spin up on demand, adding latency
Platform lock-in
- Forced GraphQL — Amplify's data layer pushes you toward GraphQL and their schema model. Not every app needs it.
- DynamoDB limitations — Limited query patterns make it unsuitable for complex relational data
- AWS knowledge required — You'll still need to understand S3, IAM, Cognito, CloudWatch, and more
Hidden complexity
- Debugging is harder — Distributed serverless logs across multiple AWS services
- Costs can spike — "Pay per request" sounds cheap until traffic grows or a bot hits your API
- Vendor lock-in — Moving away from Amplify means rewriting auth, data layer, and deployment
The alternative: self-hosting
With self-hosting on your own VPS, you get:
- Full Next.js support — Streaming, large images, no Lambda limits
- Predictable costs — Fixed monthly pricing, no surprise bills
- No cold starts — Your app runs continuously
- Use any database — PostgreSQL, MySQL, MongoDB—your choice
- Easy debugging — All logs in one place, SSH access when needed
DollarDeploy gives you the ease of Amplify with the power of self-hosting. One-click deploy to your own server, automatic HTTPS, and no vendor lock-in.