Design spec for letting a project run on **AWS ECS (Fargate or EC2)** instead of local Docker: `docs/superpowers/specs/2026-11-13-aws-ecs-host-design.md`.
Decisions recorded in the doc:
- Per-project host: Local Docker (unchanged) or AWS
- AWS connection = login (profile/SSO or access keys) + default region (option C)
- Tiered permission check (admin / workspace user / insufficient)
- Detect existing Triple-C infrastructure, then join it or deploy a new one (CloudFormation)
- Strict per-user tenancy from v1, as the default
- Claude Code login unchanged (Anthropic login or Bedrock)
- Secrets Manager delivery (or copy at connect); Hybrid storage (EFS home + ephemeral working tree); WIP push before stop on by default
- Same container image, plus an in-container agent reached over SSM port forwarding
Docs only, no code changes. Phase 1 (the `ProjectHost` abstraction refactor) follows in a separate PR.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Per-project host selection (Local Docker or AWS), AWS-CLI-style login,
tiered permission check, detect-then-join-or-deploy environments,
strict per-user tenancy by default, Secrets Manager delivery, Hybrid
EFS/ephemeral storage, in-container agent over SSM port forwarding,
and a phased plan starting with a ProjectHost abstraction refactor.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jknapp
merged commit 3a4e298849 into main2026-11-13 18:18:08 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Design spec for letting a project run on AWS ECS (Fargate or EC2) instead of local Docker:
docs/superpowers/specs/2026-11-13-aws-ecs-host-design.md.Decisions recorded in the doc:
Docs only, no code changes. Phase 1 (the
ProjectHostabstraction refactor) follows in a separate PR.🤖 Generated with Claude Code