Skip to content
inetGeek

Next.js 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.

01.

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 actually requires from the platform underneath it, and what AWS Amplify publishes about each. AWS Amplify documents 4 of the 4.

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.

Sources (1) →

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.

Sources (1) →
  • Amplify support for Next.js ↗

    “The following list describes the specific features that the Amplify Hosting compute SSR provider supports. … 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.”

    Read 2026-09-05 · official docs

Edge network

Supported

Middleware runs on every matched request before the cache is consulted. Where it executes decides how much latency it adds.

Sources (1) →

Build minutes

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.

Sources (1) →

The requirement and the reason it matters are ours. Every value beside them was read from AWS Amplify's own pages — expand a source to see the sentence it came from.

02.

What AWS Amplify documents.

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

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

Sources (1) →

Next.js features on AWS Amplify

Capabilities AWS Amplify documents specifically for Next.js, with the constraint it documents alongside each.

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 ...

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.

ISR / revalidation

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.

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).

Sources (2) →
  • Amplify support for Next.js ↗

    “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 ...”

    Read 2026-09-05 · official docs

  • Troubleshooting server-side rendered applications ↗

    “Currently, Amplify doesn't support Next.js Edge API Routes. You must use non-edge APIs and middleware when hosting your app with Amplify.”

    Read 2026-09-05 · official docs

03.

What it costs to run there.

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
Sources (1) →
04.

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.

Visit AWS Amplify documentation

Other hosts for Next.js

Next.js on Fly.ioRuns Docker images as lightweight VMs in chosen regions, billed on provisioned resources rather than plan tiers.Next.js on NetlifyPlatform for building and deploying web projects from Git to a global CDN, with serverless and edge functions.Next.js on RailwayApplication platform that builds services from a repository or Dockerfile and bills plan fees that include usage credits.Next.js on RenderManaged cloud platform that builds and runs web services, background workers, static sites and databases from Git repositories or Docker images.Next.js on VercelFrontend cloud platform for modern web applications, with Git-driven deployments and a framework-aware CDN.

Zoom out

Best hosting for Next.jsEvery provider that documents Next.js, ranked by how they document it.AWS AmplifyAWS service for hosting full-stack web applications with a Git-based continuous deployment workflow, server-side rendering support, and delivery via the AWS content delivery network.