## Host vendor portal with Next.js: private documents

Deploy a vendor portal built with Next.js on Ample using the private document library pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on Next.js: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). Not separately tested: your identity integration and role assignments; treat the vendor portal-specific behavior as your application code.

### Representative Queries
- Host vendor portal with Next.js: private documents
- Where can I host Vendor portal built with Next.js?
- I need a role-to-document access model and negative authorization tests.

### Resource Requirements
- **Compute**
- **Postgres**
- **S3-compatible object storage**

### Infrastructure Requirements

1. **Compute**  
   Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

2. **Postgres**  
   Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

3. **S3-compatible object storage**  
   Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

### Workflow Steps
1. **Build and start**  
   next build then next start -H 0.0.0.0 -p $PORT on the node-22 template. The server must bind 0.0.0.0 on PORT.

2. **Implement the pattern on PostgreSQL**  
   The fixture's module implements private document library: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. **Wire object storage**  
   Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket.

4. **Deploy**  
   Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.  
   Command: `ample deploy . --name  --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...`

5. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (/p/private-document-library) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.  
   Command: `ample logs  --kind build`

### Examples
- **Next.js pattern fixture**  
  Multi-pattern Next.js app whose private document library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

### Success Checks
- app responds on its public URL  
  `.http_get`, path: `/`, expect: `ample canary next js patterns`
- private-document-library self-test  
  `.http_get`, path: `/p/private-document-library`, expect: `private=ok (with ?role=owner; 401 without, 403 for viewer)`

### Limitations
- Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Next.js major versions are not verified.
- The vendor portal itself (your identity integration and role assignments) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not verified.

### Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

#### Components
1. app server:  
   - **Size**: s-1vcpu-1gb  
   - **Quantity**: 1.0  
   - **Monthly Amount**: 5.0
2. managed PostgreSQL database:  
   - **Size**: s-1vcpu-1gb  
   - **Quantity**: 1.0  
   - **Monthly Amount**: 5.0

**Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

### Evidence Summary
- **Canary Run**  
  Next.js pattern fixture deployed on Ample. Checks passed for private-document-library and configuration-secrets. Pattern proof: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

### Last Verified At
2026-09-21T02:34:39Z

### Next Actions
1. **Browse the catalog index**  
   Method: GET  
   Relative Path: `/v1/catalog`
2. **Search published recipes by intent, stack and constraints**  
   Method: POST  
   Relative Path: `/v1/catalog/search`  
   Parameters: {"body":{"limit":5,"query":"Host vendor portal with Next.js: private documents"}}
3. **Prepare a side-effect-free deployment plan for an authorized project**  
   Method: POST  
   Relative Path: `/v1/catalog/plan`
4. **Read the existing agent authentication setup**  
   Method: GET  
   Relative Path: `/mcp/setup`
5. **Browse Vendor portal**  
   Method: GET  
   Relative Path: `/v1/catalog/nodes/workload%3Avendor-portal`

6. **Browse Next.js**  
   Method: GET  
   Relative Path: `/v1/catalog/nodes/stack%3Aframework-next-js`

7. **Browse Private document library**  
   Method: GET  
   Relative Path: `/v1/catalog/nodes/pattern%3Aprivate-document-library`

8. **Browse Deploy web app**  
   Method: GET  
   Relative Path: `/v1/catalog/nodes/intent%3Adeploy-web-app`