Deploying a Next.js 16 fullstack app on AWS Amplify Gen 2 (SSR): six failures and how to avoid them
Getting a Next.js 16 app with an Amplify Gen 2 backend onto Amplify Hosting SSR took six failed builds — each one surfacing a layer deeper than the last. Here is the full chain: lockfile drift, the 220 MB compute cap, the deployment-spec dead end, a missing xz binary, a non-root build user, and a layer/runtime mismatch — with the fix for each.