# Configure S3-compatible access for Rails

## Summary
Object storage client for a Rails app on Ample. Verified on Rails: 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: bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via `rails server` reading PORT on the ruby-3.4 template with RAILS_ENV=production.

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

## Resource Requirements
- primitive:compute
- 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.
- **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 Rails project: bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via `rails server` reading PORT on the ruby-3.4 template with RAILS_ENV=production.
- 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**: bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via `rails server` reading PORT on the ruby-3.4 template with RAILS_ENV=production; 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. **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`

## Limitations
- Verified on the ruby-3.4 template at s-1vcpu-1gb; other sizes and Rails 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.

## Success Checks
- App responds on its public URL.
- Browser-file-uploads check from the example.

## Cost Estimate
- Currency: USD
- Monthly Amount: 5.0
- Basis: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty.
- Note: Always-on monthly price of the tested sizes; apps auto-pause when idle. Buckets are allocation-priced per quota and not included.