# Enforce private-file authorization for Astro

## Summary
Private file access for an Astro app on Ample. Verified on Astro: a role-to-document access model with negative tests (401, 403) and an authorized private-bucket round-trip (private=ok). Build and start: astro build with the @astrojs/node standalone adapter then node ./dist/server/entry.mjs on the node-22 template.

## Representative Queries
- Enforce private-file authorization for Astro
- Where can I host Enforce private-file authorization built with Astro?
- I need application identity integration, per-file access rules and negative authorization tests.

## Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

## Infrastructure Requirements
- **Compute:** Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **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.
- **S3-compatible object storage:** Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## Prerequisites
- A Astro project (astro build with the @astrojs/node standalone adapter then node ./dist/server/entry.mjs on the node-22 template)
- A PostgreSQL driver reading DATABASE_URL at runtime
- A bucket from `ample bucket create` with credentials passed as encrypted S3_* environment variables
- An Ample account token with servers:write, databases:read, buckets:read

## Workflow Steps
1. **Build and start** 
   - astro build with the @astrojs/node standalone adapter then node ./dist/server/entry.mjs on the node-22 template; the server must bind 0.0.0.0 on PORT.
2. **Create the bucket and pass its credentials** 
   - Create it once with `ample bucket create`, then pass endpoint, region, bucket and keys with --env; use path-style addressing.
   - Command: `ample deploy . --name  --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...`
3. **Authorize before touching storage** 
   - Return 401 for unauthenticated requests and 403 for the wrong role; keep the bucket unpublished and stream objects through the app.
4. **Verify** 
   - Fetch the live URL and /p/private-document-library on the example; on failure read the build and runtime logs.
   - Command: `ample logs  --kind build`

## Success Checks
- **App responds on its public URL:** `expect":"ample canary astro patterns`
- **Private-document-library check from the example:** `expect":"see the pattern fixture checks`

## Limitations
- Verified on the node-22 template at s-1vcpu-1gb; other sizes and Astro major versions are not verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
- PutObject and GetObject with path-style addressing are verified; other S3 operations are not.

## Cost Estimate
- **Currency:** USD
- **Monthly Amount:** 10.0
- **Components:**
  - app server: 1.0 @ 5.0 USD/month
  - managed PostgreSQL database: 1.0 @ 5.0 USD/month
- **Note:** Always-on monthly price of the tested sizes; apps auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Evidence Summary
- Verified private file access on Astro. Summary: A role-to-document access model with negative tests (401, 403) and an authorized private-bucket round-trip (private=ok).

## Last Verified At
2026-09-20T03:31:44Z

## Formats
- **HTML:** [Enforce private-file authorization for Astro](/content/guides/astro/private-file-access/index.html)
- **Markdown:** [Enforce private-file authorization for Astro](/content/guides/astro/private-file-access.md)
- **JSON:** [Enforce private-file authorization for Astro](https://api.ample.computer/v1/catalog/recipes/page%3Aguides%3Aastro%3Aprivate-file-access)