Skip to content

Δ5 — Completion ping (S3 FINISHED event → SNS) #39

Description

@jack-champagne

C1. One notification on terminal state so a researcher need not babysit a multi-hour solve. S3 FINISHED object event → SNS; the extension subscribes.

Acceptance (TDD): a run reaching FINISHED{completed|failed|aborted} emits exactly one notification carrying {task_id, status}.

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 (Δ5) · 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#128.

Metadata

Metadata

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