Host asset library with Spring Boot: structured data imports

Deploy a asset library built with Spring Boot on Ample using the bulk import staging 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: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping and conflict rules; treat the asset library-specific behavior as your application code.

Summary of Requirements

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

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 bulk import staging: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). 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.
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.
5. Verify: Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks.

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 asset library itself (your import format, mapping and conflict rules) is application code and was not separately tested.

Example Configuration

• Template: jvm-21
• Runtime: java
• Size: s-1vcpu-2gb
• Build Command: ./mvnw -q -DskipTests package
• Start Command: java -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)

Success Checks

1. App responds on its public URL: http_get path: /, expect: ample canary spring boot patterns.
2. Bulk-import-staging self-test: http_get path: /p/bulk-import-staging, expect: imported=2 rejected=1 restart=ok.

Prerequisites

• A Spring Boot project that builds and starts with the documented commands.
• A PostgreSQL driver reading DATABASE_URL at runtime.
• A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables.
• An Ample account token with servers:write, databases:read, and buckets:read.

Costs

• Estimated Monthly Cost: $10.00 USD
  • Components:
    • App server: s-1vcpu-1gb
    • Managed PostgreSQL database: s-1vcpu-1gb