Draft

Pattern: ecs-service

Reusable · Propel IPgolden path

The paved road for a containerized backend: ECS Fargate service + internal ALB + secrets + deploys, one module call.

flowchart LR
    ECR[(ECR image)] --> SVC[Fargate service
autoscaling]
    ALB[internal ALB] --> SVC
    SM[(Secrets Manager
placeholder + ignore_changes)] --> SVC
    SVC --> LOGS[(CloudWatch Logs)]
    style SVC fill:#EDEDFF,stroke:#3B54F7

What you get: task definition + service, ALB target/listener rules, secret seeding (changeme + lifecycle ignore_changes), log group with retention, health checks, deploy via OIDC pipeline.

Extension points: additional_containers, extra IAM statements, env/secret maps — client-specific needs compose around the module, they don't fork it.

When not to use: batch/event jobs (use Lambda patterns), or anything needing GPU/EC2 placement.

Promotion status: proven across 5 Novamera services → candidate for extraction into the versioned propel/infrastructure-modules registry (semver, pinned per client).