Configure S3-compatible access for Astro

Summary

Object storage client for an Astro app on Ample. Verified on Astro: bucket credentials delivered as encrypted S3_* environment variables and a validated PutObject/GetObject round-trip linked to a database row (upload=ok linked=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

• Configure S3-compatible access for Astro
• Where can I host Configure S3-compatible access built with Astro?
• I need exact S3 endpoint, credentials, operation requirements and an upload/download verification.

Resource Requirements

• primitive:compute
• primitive:s3-compatible-object-storage

Infrastructure Requirements

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

2. S3-compatible object storage
   Status: Verified
   Summary: 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 bucket from ample bucket create with credentials passed as encrypted S3_* environment variables
• An Ample account token with servers:write, buckets:read

Steps

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.

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=...

Verify

Fetch the live URL and /p/browser-file-uploads on the example; on failure read the build and runtime logs.
Command:
ample logs --kind build

Examples

Astro pattern fixture

Verified object storage client on Astro.
Source Ref: tests/deploy-canaries/astro-patterns

Success Checks

1. App responds on its public URL
   Kind: http_get
   Path: /
   Expect: ample canary astro patterns
2. Browser-file-uploads check from the example
   Kind: http_get
   Path: /p/browser-file-uploads
   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.
• PutObject and GetObject with path-style addressing are verified; other S3 operations are not.

Cost Estimate

• Currency: USD
• Monthly Amount: 5.0
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • Name: app server
    Size: s-1vcpu-1gb
    Quantity: 1.0
    Monthly Amount: 5.0
• 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

• Kind: canary_run
  Summary: Astro pattern fixture deployed on Ample; for this guide: bucket credentials delivered as encrypted S3_* environment variables and a validated PutObject/GetObject round-trip linked to a database row (upload=ok linked=ok).
  Observed At: 2026-09-20T03:31:44Z
  Expires At: 2027-03-19T03:31:44Z

Next Actions

• Browse the catalog index: GET /v1/catalog
• Search published recipes by intent, stack and constraints: POST /v1/catalog/search
• Prepare a side-effect-free deployment plan for an authorized project: POST /v1/catalog/plan
• Read the existing agent authentication setup: GET /mcp/setup
• Browse Astro: GET /v1/catalog/nodes/stack%3Aframework-astro
• Browse Connect app to storage: GET /v1/catalog/nodes/intent%3Aconnect-app-to-storage
• Browse Browser file uploads: GET /v1/catalog/nodes/pattern%3Abrowser-file-uploads