Skip to content

Δ2 — API submission front-end (POST /solves → Step Function, credentialed) #36

Description

@jack-champagne

C1. An authenticated API (API Gateway + lambda) POST /solves accepting the LLM-authored script + params + an overridable cap; lands the script in the upload bucket and starts harmoniqs-analysis-step-function; returns task_id. Sits alongside the existing SES path. Auth = the manually-provisioned per-user credential the extension ingests (SSO is partial internally / absent for external labs).

Acceptance (TDD): posting with a valid credential creates a run record (task_status=Pending) + returns a task_id; an invalid/absent credential → 401 and no instance launched.

Gate: blocked by the wk-3 freeze — run-dir contract + SchemaPackage v0 (amicode #15 + the #28–31 stack). RemoteExecutor/the S3 layout is the run-dir contract, so do not start until that lands.

📄 Refs: Spec armonissima/specs/spec-20260628-amicode-cloud-solve-service.md (Δ2) · phased plan §5a (plan-20260603-124231-amicode-phased-build) · aws-infra/INFRASTRUCTURE.mdThe Analysis Pipeline (reuse step_function/ec2_launch_template/dynamodb/runner_image).

Evolve, not build — a working v0 (the aws-infra Analysis Pipeline) already does size→S/M/L EC2→julia→S3→email→terminate. Validate on staging (mirrors prod), then two-step promote.

🏗 Implementation repo: aws-infra (Terraform / lambda / Image Builder). Infra-side reference: harmoniqs/aws-infra#125.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requesttrack:cloudTrack C — company compute / cloud solve-service

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions