Platform target

AWS Amplify Hosting

Amplify has a filesystem deployment specification for framework authors. Nift emits the static form of that native bundle.

nift init --target=amplify
nift build

What Nift creates

.amplify-hosting/
├── deploy-manifest.json
└── static/
    ├── index.html
    └── assets/...

The manifest uses deployment-spec version 1, identifies Nift as the framework, and contains the required catch-all route targeting Amplify's Static primitive.

Pure static starter.

No compute/ directory is created. Amplify's deployment specification only requires compute when the application actually uses that primitive.

Adding compute

Amplify's compute primitive runs a self-contained Node.js HTTP server from .amplify-hosting/compute/default; the manifest then needs matching compute metadata/routes. Treat that as Amplify runtime code beside the Nift-generated static tree, not as Nift template execution.

Routing, headers and environment

The deployment manifest supports routing targets; Amplify Hosting also supports build environment variables and custom response headers (including a repository-level customHttp.yml option). Extend those provider files when required rather than embedding AWS concepts in Nift templates.

Official references: deployment specification, build settings, and custom headers.

Next platformAzure →