Next.js standalone on AWS Lambda (Web Adapter): ISR/fetch revalidate silently does nothing

In a Next.js standalone container on Lambda, the app dir is read-only, so ISR and fetch revalidate fail with "Failed to update prerender cache ... ENOENT: mkdir /app/.next/cache" in CloudWatch, and pages go out with Cache-Control: private, no-cache, no-store. export const revalidate = N then has no effect: every view runs the Lambda and may hit the backend again. Fix it by pointing .next/cache at /tmp (a symlink in the Dockerfile) or adding a custom cacheHandler. Then check that responses carry s-maxage, so a CDN in front (Amplify honours it) can cache them.