page:recipes:ai chat application:spring boot:artifact storage

Host ai chat application with Spring Boot: stored input and output artifacts

Deploy a ai chat application 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 ai chat application-specific behavior as your application code.

Representative Queries

• Host ai chat application with Spring Boot: stored input and output artifacts
• Where can I host AI chat application built with Spring Boot?
• I need an input/output artifact contract, object metadata and access boundaries.

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 Spring Boot project that builds and starts with the documented commands (./mvnw -q -DskipTests package) producing one application jar, then java -jar on the jvm-21 template (Temurin JDK 21) with server.port read from PORT.
• A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
• A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables.
• An Ample account token with servers:write, databases:read, buckets:read.

Workflow Steps

1. Build and start: ./mvnw -q -DskipTests package (or the Gradle wrapper), then java -jar on the jvm-21 template.
2. Implement the pattern on PostgreSQL: The fixture's module implements generated downloads; copy the approach into your schema.
3. Wire object storage: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values.
4. Deploy: Run the synchronous deploy once and read the result.
5. Verify: Fetch the live URL and the pattern self-test route(s).

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App Server: s-1vcpu-1gb, 1.0, 5.0
  • Managed PostgreSQL Database: s-1vcpu-1gb, 1.0, 5.0

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.
• Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.

Next Actions

• Browse the catalog index
• Search published recipes
• Prepare a side-effect-free deployment plan for an authorized project
• Read the existing agent authentication setup
• Browse AI chat application
• Browse Spring Boot
• Browse Generated downloads
• Browse Deploy AI app