page:recipes:crm:spring boot:csv imports
Host crm with Spring Boot: CSV imports
Deploy a crm 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 crm-specific behavior as your application code.
Prerequisites
- A Spring Boot project that builds and starts with the documented commands (./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)
- A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
- A bucket from
ample bucket createwith its credentials passed as encrypted S3_* environment variables - An Ample account token with servers:write, databases:read, buckets:read
Workflow Steps
Build and start
./mvnw -q -DskipTests package(or the Gradle wrapper) producing one application jar, thenjava -jaron the jvm-21 template (Temurin JDK 21) with server.port read from PORT. The server must bind 0.0.0.0 on PORT.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). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.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.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 --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...Verify
Fetch the live URL and the pattern self-test route(s) (/p/bulk-import-staging) from the example; then run your own checks. On failure readample logs --kind buildthen--kind runtime.
Command:ample logs --kind build
Success Checks
- App responds on its public URL: Expected: ample canary spring boot patterns
- Bulk-import-staging self-test: Expected: imported=2 rejected=1 restart=ok
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 crm itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
Cost Estimate
Monthly Amount: $10.00 (USD)
- Components:
- App server (s-1vcpu-1gb): $5.00
- Managed PostgreSQL database (s-1vcpu-1gb): $5.00
Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.
Example
Title: Spring Boot pattern fixture
Description: Multi-pattern Spring Boot app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
Source Ref: tests/deploy-canaries/spring-boot-patterns
Evidence Summary
- Canary Run: Spring Boot pattern fixture deployed on Ample; checks passed for bulk-import-staging and configuration-secrets.
Observed At: 2026-09-21T02:34:39Z
Implementation Revision: 1d28ae0-dirty (CLI 0.1.21)
Expires At: 2027-03-20T02:34:39Z
Additional Infomation
- Framework: Spring Boot
- Workload: CRM
- Release Status: Published
- Support Status: Verified
- Execution Status: Ready
- Docs Only: false