Jon Chery
031887ec56
Contract surface redesign: - New top-level fields: id (3-6 char acronym → stack.name), name (full → stack.title), infrastructure (map keyed by module name, replaces module:) - Drop uses: field (dead reference; version pin lives in CI workflow uses: line) - Drop top-level module/inputs (now nested under infrastructure map) - Per-module optional version (defaults to latest published from registry) - Multi-module contracts: one file deploys N modules in one pipeline run, resource IDs namespaced with module name to avoid collisions - stack.schema.json: add optional title field for display name Rename: - pipelines/deploy.yaml → pipelines/contract.yml (declarative spec, not a pipeline) - pipelines/ci.yaml → pipelines/ci.yml - All 44 .yaml files → .yml repo-wide (contracts, module examples, kyverno policies) - .acdl/contract.yaml → .acdl/contract.yml Resolver (core/contract_resolver.py): - Rewrite resolve() to loop infrastructure map, default version to latest, merge module fragments into one stack with namespaced resource IDs - _latest_version() picks highest non-deprecated from registry - _namespace_resources() prefixes IDs + rewrites ref: expressions for multi-module - Single-module path: unprefixed IDs (backward compatible) Verification: - 494 tests pass (0 contract-shape failures) - Local E2E passes (contract → resolver → adapter → local ECS HTTP 200 → outbox) ---ci--- project: acdl phase: 57 milestone: v1.10.2 status: execute ---/ci---
124 lines
4.2 KiB
Markdown
124 lines
4.2 KiB
Markdown
# ecs-service — ECS Fargate service (task definition + service)
|
|
|
|
> **Module kind:** primitive | **Version:** 1.0.0
|
|
|
|
An ECS Fargate service with its task definition. Runs a container image
|
|
on Fargate, optionally behind an ALB target group. This is a
|
|
multi-resource module: it creates a task definition and a service that
|
|
runs it.
|
|
|
|
## Resources
|
|
|
|
| Resource | Type | Purpose |
|
|
|----------|------|---------|
|
|
| task_definition | `aws_ecs_task_definition` | Fargate task definition with container image, CPU, memory, port, env |
|
|
| service | `aws_ecs_service` | Fargate service running the task definition in a cluster + subnets |
|
|
|
|
## Inputs
|
|
|
|
| Name | Type | Required | Default | Description |
|
|
|------|------|----------|---------|-------------|
|
|
| `image` | string | yes | — | ECR image URL for the task container |
|
|
| `port` | number | yes | — | Container port the service listens on |
|
|
| `cpu` | number | no | 256 | Task CPU units (Fargate) |
|
|
| `memory` | number | no | 512 | Task memory in MiB (Fargate) |
|
|
| `env` | string | no | — | Environment variables as a JSON map string |
|
|
| `cluster_arn` | arn | yes | — | ECS cluster ARN (from `ecs-cluster`) |
|
|
| `subnets` | string | yes | — | Comma-separated subnet ids (from `vpc`) |
|
|
| `security_group` | string | yes | — | Security group id for the service ENIs |
|
|
| `lb_target_group_arn` | arn | no | — | Optional ALB target group ARN (from `alb`) |
|
|
| `region` | string | yes | — | AWS region the service is created in |
|
|
|
|
## Outputs
|
|
|
|
| Name | Type | Description |
|
|
|------|------|-------------|
|
|
| `service_arn` | arn | The ECS service ARN |
|
|
| `task_def_arn` | arn | The ECS task definition ARN |
|
|
|
|
## Usage
|
|
|
|
```json
|
|
{
|
|
"id": "service",
|
|
"type": "aws:ecs:task_definition",
|
|
"module": "ecs-service@1.0.0",
|
|
"inputs": {
|
|
"image": "581513795199.dkr.ecr.us-east-1.amazonaws.com/acdl-microservice:latest",
|
|
"port": 8080,
|
|
"cpu": 256,
|
|
"memory": 512,
|
|
"cluster_arn": "ref:cluster.cluster_arn",
|
|
"subnets": "ref:vpc.subnet_ids",
|
|
"security_group": "ref:roles.role_arn",
|
|
"region": "us-east-1"
|
|
}
|
|
}
|
|
```
|
|
|
|
The `image`, `port`, and `env` inputs are compiled into a
|
|
`container_definitions` JSON block by the adapter. The service is
|
|
placed in the cluster with the given subnets and security group, and
|
|
optionally wired to the ALB target group if `lb_target_group_arn` is
|
|
provided.
|
|
|
|
## Compliance extension points
|
|
|
|
- **CloudWatch Logs** — add `logConfiguration` to the container definition with a log group + retention policy (SOX, SOC2 CC7.2, DORA ICT incident logging).
|
|
- **Task execution role separation** — add a separate `aws_iam_role` for execution vs. the task role (SOC2 CC6.3 segregation of duties at runtime).
|
|
- **Secrets injection** — add `secrets` block referencing AWS Secrets Manager / SSM Parameter Store with KMS encryption (SOC2 CC6.1.
|
|
- **Execute command** — add `enable_execute_command` with KMS encryption for session audit (SOC2 CC7.2).
|
|
- **Deployment circuit breaker** — add `deployment_circuit_breaker` block for resilience (SOC2 CC9.1, DORA operational resilience).
|
|
- **Health check** — add a `health_check` block to the target group (currently missing despite the contract schema having a healthcheck field).
|
|
|
|
## Examples
|
|
|
|
Validated example contracts are in [`examples/`](examples/). The platform-test
|
|
pipeline validates them against `schemas/contract.schema.json`.
|
|
|
|
### Simple
|
|
|
|
A minimal deployment:
|
|
|
|
[`examples/simple.yml`](examples/simple.yml)
|
|
```yaml
|
|
environment: dev
|
|
id: svc
|
|
infrastructure:
|
|
ecs-service:
|
|
inputs:
|
|
image: public.ecr.aws/docker/library/nginx:latest
|
|
name: my-service
|
|
port: 80
|
|
region: us-east-1
|
|
version: 1.0.0
|
|
name: ecs-service
|
|
```
|
|
|
|
### Complex
|
|
|
|
A production deployment with optional inputs:
|
|
|
|
[`examples/complex.yml`](examples/complex.yml)
|
|
```yaml
|
|
environment: dev
|
|
id: svc
|
|
infrastructure:
|
|
ecs-service:
|
|
inputs:
|
|
env:
|
|
ENVIRONMENT: production
|
|
LOG_LEVEL: info
|
|
image: public.ecr.aws/docker/library/nginx:latest
|
|
name: my-production-service
|
|
port: 8080
|
|
region: us-east-1
|
|
version: 1.0.0
|
|
name: ecs-service
|
|
```
|
|
|
|
## Versioning
|
|
|
|
`1.0.0` — interface MAJOR, behavior MINOR, lifecycle PATCH. MAJOR bumps
|
|
require a new registry entry (immutable publication); old entries enter
|
|
a 12-month deprecation window. |