• Next.js app deployed serverlessly via the nextjs-web resource — Lambda + S3 + CloudFront CDN.
• Zero-config deployment. Includes a server-rendered page and an API route example.
• Optionally add a database — see commented section in stacktape.yml.
• This project includes a pre-configured stacktape.yml configuration. The configured infrastructure is described in the stack description section

1. AWS account. If you don't have one, create new account here.

2. Stacktape account. If you don't have one, create new account here.

3. Stacktape installed.

iwr https://installs.stacktape.com/windows.ps1 -useb | iex

curl -L https://installs.stacktape.com/linux.sh | sh

curl -L https://installs.stacktape.com/macos.sh | sh

curl -L https://installs.stacktape.com/macos-arm.sh | sh

To initialize the project, use

stacktape init --starterId nextjs-serverless

The deployment will take ~5-15 minutes. Subsequent deploys will be significantly faster.

stacktape deploy --projectName <<project-name>> --stage <<stage>> --region <<region>>

stacktape codebuild:deploy --stage <<stage>> --region <<region>> --projectName <<project-name>>

After a successful deployment, some information about the stack will be printed to the terminal (URLs of the deployed services, links to logs, metrics, etc.).

• Open the CDN URL printed to the terminal after deploy to see your app.
• Test the API route at <CDN_URL>/api/hello.

• Stacktape deployments use AWS CloudFormation under the hood. It brings a lot of guarantees and convenience, but can be slow for certain use-cases.

• To speed up the deployment, you can use the --hotSwap flag which avoids using Cloudformation.

• Hotswap deployments work only for source code changes (for lambda function, containers and batch jobs) and for content uploads to buckets.

• If the update deployment is not hot-swappable, Stacktape will automatically fall back to using a Cloudformation deployment.

stacktape deploy --hotSwap --stage <<stage>> --region <<region>> --projectName <<project-name>>

• If you no longer want to use your stack, you can delete it.
• Stacktape will automatically delete every infrastructure resource and deployment artifact associated with your stack.

stacktape delete --stage <<stage>> --region <<region>>

Stacktape uses a simple stacktape.yml configuration file to describe infrastructure resources, packaging, deployment pipeline and other aspects of your project.

You can deploy your project to multiple environments (stages) - for example production, staging or dev-john. A stack is a running instance of an project. It consists of your application code (if any) and the infrastructure resources required to run it.

The configuration for this project is described below.

• Every resource must have an arbitrary, alphanumeric name (A-z0-9).
• Stacktape resources consist of multiple underlying AWS or 3rd party resources.

The app runs serverlessly using the nextjs-web resource, which requires zero configuration.

Behind the scenes, it creates a Lambda function for server-side rendering, an S3 bucket for static assets, and a CloudFront CDN for global delivery.

resources:
  web:
    type: nextjs-web
    properties:
      appDirectory: ./

To connect a database, add a relational-database resource and list it in connectTo. The connection string is automatically injected as an environment variable.