Next.js On AWS
summary
Claim: at recording time aws amplify only hosts statically exported Next.js sites—no SSR or API routes—while the serverless-next component deploys full Next.js (SSG SSR and /api routes) to CloudFront/Lambda and works end to end; demo adds an /api/speakers endpoint and redeploys via npx serverless. Practical detail: the component example references version 1.16.0. For server-side auth Amplify exposes withSSRContext so getServerSideProps can call API and Auth with correct headers and sessions.
AI-written summary · about
chapters (8)
- 0:00Start
- 2:14SSR Server-side rendering
- 2:50Speed/ performance • Search Engine Optimization • Resiliency / scalability
- 3:59Server rendered • On-demand-renders the page into HTML on
- 4:29WHICH ONE? SSR
- 10:15DEPLOYING
- 16:33API INTERACTIONS
- 16:52SSR CONFIGURATION
related talks
26mBuild, deploy, and host performant server-side apps
34mFrom Front-end to Full Stack
42mBuilding Serverless Web Applications with AWS
27mFull-Stack Application Development Completely Serverless
28mLive Coding on AWS Amplify
06mAWS Lambda + AWS Gateway + React = AWEsome
38mLift and Shift a WebApp to Serverless. Is that even possible?
14mReact on the Jamstack