Host client portal with Flask: private documents

Deploy a client portal built with Flask on Ample using the private document library 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 role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). Not separately tested: your identity integration and role assignments; treat the client portal-specific behavior as your application code.

Representative Queries

• Host client portal with Flask: private documents
• Where can I host Client portal built with Flask?
• I need a role-to-document access model and negative authorization tests.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

Infrastructure Requirements

1. Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. 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.
3. 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 Flask project that builds and starts with the documented commands (pip install into .ample/python from requirements.txt, then waitress from app.py reading PORT on the python-3.12 template).
• 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: pip install into .ample/python from requirements.txt, then waitress from app.py reading PORT on the python-3.12 template.
2. Implement the pattern on PostgreSQL: Copy the role-to-document access model with negative tests 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.
4. Deploy: Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked).
5. Verify: Fetch the live URL and the pattern self-test route(s) (/p/private-document-library) from the example; then run your own checks.

Success Checks

• App responds on its public URL (expected response: ample canary flask patterns).
• Private-document-library self-test (expected response: private=ok, 401 without identity, 403 for viewer).

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 client portal itself (your identity integration and role assignments) is application code and was not separately tested.

Cost Estimate

• Total Monthly Amount: $10.00 USD
• Components:
  • app server (s-1vcpu-1gb): $5.00
  • managed PostgreSQL database (s-1vcpu-1gb): $5.00
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Evidence Summary

1. Canary Run: Flask pattern fixture deployed on Ample; checks passed for private-document-library and configuration-secrets.
2. Implementation Revision: 50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty (CLI 0.1.21).

Next Actions

• Browse the catalog index
• Search published recipes by intent, stack and constraints
• Prepare a side-effect-free deployment plan for an authorized project
• Read the existing agent authentication setup
• Browse Client portal
• Browse Flask
• Browse Private document library
• Browse Deploy web app