page:recipes:csv import tool:spring boot:data exports

Host csv import tool with Spring Boot: data exports

Deploy a csv import tool 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 csv import tool-specific behavior as your application code.

Representative Queries

• Host csv import tool with Spring Boot: data exports
• Where can I host CSV import tool built with Spring Boot?
• I need a scoped export format, artifact generation and authorized download procedure.

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 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. Re-running with no change is a no-op.
5. Verify: Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads) from the example; then run your own checks.

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.

Success Checks

• App responds on its public URL
• Generated-downloads self-test

Limitations

• Verified on the jvm-21 template at s-1vcpu-2gb with the example fixture.
• The csv import tool itself (your export formats, retention policy and entitlement model) is application code and was not separately tested.

Cost Estimate

• Monthly Amount: 10.0 USD
  • App server: 5.0 USD for size s-1vcpu-1gb
  • Managed PostgreSQL database: 5.0 USD for size s-1vcpu-1gb
  • Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Formats

• HTML
• Markdown
• JSON

Next Actions

• Browse the catalog index: /v1/catalog
• Search published recipes: /v1/catalog/search
• Prepare a side-effect-free deployment plan: /v1/catalog/plan
• Read the existing agent authentication setup: /mcp/setup
• Browse CSV import tool: /v1/catalog/nodes/workload%3Acsv-import-tool
• Browse Spring Boot: /v1/catalog/nodes/stack%3Aframework-spring-boot
• Browse Generated downloads: /v1/catalog/nodes/pattern%3Agenerated-downloads
• Browse Deploy web app: /v1/catalog/nodes/intent%3Adeploy-web-app