Host reporting dashboard with Flask: structured data imports

Deploy a reporting dashboard built with Flask 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 Flask: 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 reporting dashboard-specific behavior as your application code.

Representative Queries

• Host reporting dashboard with Flask: structured data imports
• Where can I host Reporting dashboard built with Flask?
• I need a workload-specific import mapping, conflict rules and restart behavior.

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: pip install into .ample/python from requirements.txt, then waitress from app.py reading PORT on the python-3.12 template. 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). 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 --public --start "python3 app.py" --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/bulk-import-staging) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
   • Command: ample logs --kind build

Success Checks

• App responds on its public URL
  • Kind: http_get
  • Path: /
  • Expect: ample canary flask patterns
• Bulk-import-staging self-test
  • Kind: http_get
  • Path: /p/bulk-import-staging
  • Expect: imported=2 rejected=1 restart=ok

Limitations

• Verified on the python-3.12 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Flask major versions are not verified.
• The reporting dashboard 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.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.
• PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • App Server: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
  • Managed PostgreSQL Database: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.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.

Evidence Summary

• Kind: canary_run
  • Summary: Flask pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then waitress from app.py reading PORT on the python-3.12 template); checks passed for bulk-import-staging and configuration-secrets. Pattern proof: 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).
  • Observed At: 2026-09-21T01:14:18Z
  • Implementation Revision: 50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty (CLI 0.1.21)
  • Expires At: 2027-03-20T01:14:18Z

Formats

• HTML: https://ample.computer/recipes/reporting-dashboard/flask/data-imports
• Markdown: https://ample.computer/recipes/reporting-dashboard/flask/data-imports.md
• JSON: https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Areporting-dashboard%3Aflask%3Adata-imports

Next Actions

1. Browse the catalog index
   • Method: GET
   • Relative Path: /v1/catalog
2. Search published recipes by intent, stack and constraints
   • Method: POST
   • Relative Path: /v1/catalog/search
3. Prepare a side-effect-free deployment plan for an authorized project
   • Method: POST
   • Relative Path: /v1/catalog/plan
4. Read the existing agent authentication setup
   • Method: GET
   • Relative Path: /mcp/setup
5. Browse Reporting dashboard
   • Method: GET
   • Relative Path: /v1/catalog/nodes/workload%3Areporting-dashboard
6. Browse Flask
   • Method: GET
   • Relative Path: /v1/catalog/nodes/stack%3Aframework-flask
7. Browse Bulk import staging
   • Method: GET
   • Relative Path: /v1/catalog/nodes/pattern%3Abulk-import-staging
8. Browse Deploy web app
   • Method: GET
   • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app