v0.1.1

• Fixed / being interpreted as 404
• Trying a fix to support Next.js redirect

v0.1.0

• added support for 404 page

v0.0.5

• Add automatic version bump

v0.0.4

• Fix bug on routing

v0.0.3

• Fix bug on api handler

v0.0.1

Install

npm i -g aws-next

Usage

Build your Next.js app (e.g. next build), then navigate to the root of your Next.js project and run:

$ aws-next

This will output the build artifacts under .aws-next folder. The artifacts are meant to be deployed using AWS CDK.

Artifacts

• s3: contains static assets to be deployed to AWS S3
• default-lambda: contains the lambda@edge code to handle all page and assets requests
• api-lambda: contains the lambda@edge code to handle all api requests

Inject environment variables

Lambda@edge does not support environment variables. To overcome this you can bundle your enviroment variables into your Next.js deploy. Alternatively, this CLI injects into process.env custom headers defined from the Cloudfront distribution that starts with X-ENV-.

v0.0.1-beta.3

Usage

In your Next.js root folder, run:

npx aws-next

v0.0.1-beta.2

Usage

In your Next.js root folder, run:

npx aws-next

v0.0.1-beta.1

Usage

In your Next.js root folder, run:

npx aws-next