# Configure S3-compatible access for Hono

## Summary
Object storage client for a Hono app on Ample. Verified on Hono: 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: npm install and npm run start with @hono/node-server on the node-22 template.

## Representative Queries
- Configure S3-compatible access for Hono
- Where can I host Configure S3-compatible access built with Hono?
- 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.  
   - [Learn more](https://discover/primitive/compute)
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.  
   - [Learn more](https://discover/primitive/s3-compatible-object-storage)

## Prerequisites
- A Hono project (npm install and npm run start with @hono/node-server 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

## Workflow Steps
1. ### Build and start  
   npm install and npm run start with @hono/node-server 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.  
   ```bash  
   ample deploy . --name  --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...  
   ```  
3. ### Verify  
   Fetch the live URL and /p/browser-file-uploads on the example; on failure read the build and runtime logs.  
   ```bash  
   ample logs  --kind build  
   ```

## Limitations
- Verified on the node-22 template at s-1vcpu-1gb; other sizes and Hono 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:  
     - **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:** Hono pattern fixture deployed on Ample (npm install and npm run start with @hono/node-server on the node-22 template); 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-21T01:14:18Z
- **Expires At:** 2027-03-20T01:14:18Z

## Next Actions
- **Browse the catalog index** - GET /v1/catalog  
- **Search published recipes by intent** - POST /v1/catalog/search  
- **Prepare a deployment plan** - POST /v1/catalog/plan  
- **Read the existing agent authentication setup** - GET /mcp/setup  
- **Browse Hono** - GET /v1/catalog/nodes/stack%3Aframework-hono  
- **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