# Next.js on AWS Amplify

Canonical: https://inetgeek.com/stacks/nextjs-on-aws-amplify/

AWS Amplify publishes its own guide for deploying Next.js.

React framework with file-based routing, server components and a build step that produces both static and server-rendered output.

## What Next.js needs

Every host claims to run Next.js, so the claim on its own decides nothing. These are the things Next.js requires from the platform underneath it, and what AWS Amplify publishes about each. AWS Amplify documents 6 of the 6.

| Requirement | AWS Amplify | Why it matters |
| --- | --- | --- |
| Max request duration | 15 minutes (maximum execution time of an SSR compute execution instance) | Server components and route handlers run per request. The wall-clock ceiling decides whether a slow upstream API or a model response can finish at all. |
| Streaming response limit | Next.js streaming is listed as an unsupported feature of the Amplify Hosting compute SSR provider — i.e. streamed responses are not available at all, rather than bounded by a duration or size. Platform-wide (Amplify Hosting has no plan tiers). | The App Router streams the dynamic parts of a page as they resolve. A host that buffers the whole response first removes the benefit. |
| Edge network | Supported | Middleware runs on every matched request before the cache is consulted. Where it executes decides how much latency it adds. |
| Build allowance | 1,000 build minutes per month at no cost with AWS Free Tier; $0.01 per minute for a Standard Instance thereafter | A large Next.js app prerenders at build time, so the build allowance is a recurring cost rather than a one-off. |
| Git deployment | Supported | The Next.js workflow assumes a push builds and ships. A host without git-triggered deploys means wiring CI yourself before the first deploy, which is most of the setup cost. |
| Concurrent builds | 5 concurrent jobs per Region by default, adjustable via a quota increase request | Next.js builds are slow enough that queueing is felt. One build at a time is workable alone and becomes the bottleneck the moment two people merge in the same hour. |

- Max request duration source: https://docs.aws.amazon.com/amplify/latest/userguide/ssr-deployment-specification.html
- Streaming response limit source: https://docs.aws.amazon.com/amplify/latest/userguide/ssr-amplify-support.html
- Edge network source: https://docs.aws.amazon.com/amplify/latest/userguide/welcome.html
- Build allowance source: https://aws.amazon.com/amplify/pricing/
- Git deployment source: https://docs.aws.amazon.com/amplify/latest/userguide/welcome.html
- Concurrent builds source: https://docs.aws.amazon.com/amplify/latest/userguide/quotas-chapter.html

## What AWS Amplify documents

> Use the following instructions to deploy a new Next.js SSR app.

Source: https://docs.aws.amazon.com/amplify/latest/userguide/deploy-nextjs-app.html

### Next.js features on AWS Amplify

- **image_optimization**: Supported — You can deploy apps built with Next.js versions up through Next.js 15, with features such as image optimization and middleware. — Supported features: ... Image optimization ... ([source](https://docs.aws.amazon.com/amplify/latest/userguide/ssr-amplify-support.html))
- **middleware**: Limited — Currently, Amplify doesn't support Next.js Edge API Routes. You must use non-edge APIs and middleware when hosting your app with Amplify. ([source](https://docs.aws.amazon.com/amplify/latest/userguide/troubleshooting-SSR.html))
- **isr**: Limited — Starting with version 12.2.0, Next.js supports Incremental Static Regeneration (ISR) to manually purge the Next.js cache for a specific page. However, Amplify doesn't currently support On-Demand ISR. If your app is using Next.js on-demand revalidation, this feature won't work when you deploy your app to Amplify. ([source](https://docs.aws.amazon.com/amplify/latest/userguide/troubleshooting-SSR.html))
- **streaming_ssr**: Not supported — Unsupported features: Edge API Routes (Edge middleware is not supported); On-Demand Incremental Static Regeneration (ISR); Next.js streaming; Running middleware on static assets and optimized images; Executing code after a response with unstable_after (Experimental feature released with Next.js 15). ([source](https://docs.aws.amazon.com/amplify/latest/userguide/ssr-amplify-support.html))

## What it costs to run there

|  | AWS Amplify |
| --- | --- |
| Entry paid plan | No monthly minimum — Amplify Hosting is billed per unit. A representative month for one small app, priced at Amplify's published rates: 100 build minutes ($1.00), 5 GB stored ($0.11), 100 GB served ($15.00), with SSR requests inside the free 500,000 — about $16.11. Our arithmetic on Amplify's rates, not a price Amplify quotes, and it moves with traffic: egress is 93% of it. Recorded without a magnitude for that reason. |
| Pricing model | Usage-based; pay for what you use, with no monthly minimum |
| When you exceed a cap | Billed automatically: pay-as-you-go with no monthly minimums; storage charges keep recurring until the app is deleted |

- Entry paid plan source: https://aws.amazon.com/amplify/pricing/
- Pricing model source: https://aws.amazon.com/amplify/pricing/
- When you exceed a cap source: https://aws.amazon.com/amplify/pricing/

## Whether it suits you

Front-end apps deployed from Git onto AWS with usage-based pricing and no monthly minimum, including 1,000 build minutes and 15 GB of transfer under the free tier.

Consider something else if: Egress beyond the free allowance is $0.15 per GB, which is the highest of the platforms compared here, and SSR compute is capped at 15 minutes.

Written by Palash Bagchi on 2026-09-05. This is a recommendation, not a sourced fact — it carries no citation because it is an opinion.

## Related

- Best hosting for Next.js: https://inetgeek.com/stacks/nextjs/
- AWS Amplify: https://inetgeek.com/hosting/aws-amplify/