Host order tracking with Spring Boot: authorized file delivery

Deploy a order tracking built with Spring Boot on Ample using the generated downloads 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 Spring Boot: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the order tracking-specific behavior as your application code.

Representative Queries

• Host order tracking with Spring Boot: authorized file delivery
• Where can I host Order tracking built with Spring Boot?
• I need a file entitlement model and an application-enforced download authorization flow.

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.

Workflow Steps

1. Build and start
   ./mvnw -q -DskipTests package (or the Gradle wrapper) producing one application jar, then java -jar on the jvm-21 template (Temurin JDK 21) with server.port read from PORT. The server must bind 0.0.0.0 on PORT.
2. Implement the pattern on PostgreSQL
   The fixture's module implements generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). 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 <app-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/generated-downloads) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
   Command: ample logs --kind build

Examples

• Spring Boot pattern fixture: Multi-pattern Spring Boot app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules. Source: tests/deploy-canaries/spring-boot-patterns

Success Checks

• App responds on its public URL: http_get on / expects ample canary spring boot patterns
• Generated-downloads self-test: http_get on /p/generated-downloads expects export=ok rows=3 (with ?token=...; 401 without)

Limitations

• Verified on the jvm-21 template at s-1vcpu-2gb with the example fixture; other sizes, templates and Spring Boot major versions are not verified. The order tracking itself (your export formats, retention policy and entitlement model) is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.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.
• Components:
  • App server: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
  • Managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0

Next Actions

• Browse the catalog index: GET /v1/catalog
• Search published recipes by intent, stack and constraints: POST /v1/catalog/search with body { "limit": 5, "query": "Host order tracking with Spring Boot: authorized file delivery" }
• Prepare a side-effect-free deployment plan for an authorized project: POST /v1/catalog/plan with body { "inputs": {}, "projectId": "", "recipeId": "page:recipes:order-tracking:spring-boot:download-delivery", "recipeRevision": "r1" }
• Read the existing agent authentication setup: GET /mcp/setup
• Browse Order tracking: GET /v1/catalog/nodes/workload%3Aorder-tracking
• Browse Spring Boot: GET /v1/catalog/nodes/stack%3Aframework-spring-boot
• Browse Generated downloads: GET /v1/catalog/nodes/pattern%3Agenerated-downloads
• Browse Deploy web app: GET /v1/catalog/nodes/intent%3Adeploy-web-app