Does Amplify Hosting Support Next.js 16?
Treat Next.js 16 on Amplify as a compatibility test while AWS documentation still lists managed SSR support through Next.js 15.
Treat Next.js 16 on Amplify as a compatibility test while AWS documentation still lists managed SSR support through Next.js 15.
Let Proxy shape navigation without turning it into an authorization layer that duplicates Amplify Auth and Data rules.
Design precise record and route invalidation for environments that support it while treating Amplify Hosting's documented lack of on-demand revalidation as a deployment boundary.
Use a canary to learn whether Amplify buffers or rejects a streaming response while production retains a complete non-streaming path.
Test a Next.js 16 upgrade against the application's Amplify SSR paths while keeping the current lockfile ready to restore.
Cache public Amplify records without letting a request cookie or owner-scoped response leak into a shared Next.js cache entry.
Strapi was a good CMS for Terry Hunt Dev. I began moving the backend to Amplify Gen 2 because I wanted to learn a different way to model, secure, and deploy application data.
Use small Node Route Handlers around Amplify services instead of assuming Edge APIs will work on Amplify Hosting.
Treat every Server Action call as untrusted input before it reaches an Amplify Data mutation.
Put the request-time session check in a small Server Component boundary instead of making every public layout depend on cookies.
Treat generated Amplify outputs as client configuration while credentials and private provider values remain on the server.
Move an Amplify Gen 2 application from a personal sandbox to production without mixing backend outputs, secrets, or branch data.
Plan public, signed-in, owner, group, and server access before an Amplify Gen 2 data model reaches production.
Trace localhost 401, DNS, empty-data, and login failures back to the Amplify backend that generated amplify_outputs.json.
Design scheduled publishing with UTC timestamps, idempotent mutations, bounded retries, cache revalidation, and visible failure records.
A practical Amplify Gen 2 architecture built around user journeys, resource ownership, authorization, and deployment boundaries.
Build an Amplify Gen 2 contact form that validates input, sends server-side email, protects secrets, and reports delivery failures.
Separate public configuration, function settings, and secrets across Amplify Gen 2 sandboxes and branch deployments.
Plan a Strapi deployment on AWS around network boundaries, workload identity, database and media recovery, secret handling, observability, and updates.
Discover more topics and tutorials across the blog