---ci--- project: acdl phase: 39 milestone: v1.9 status: execute ---/ci--- Phase 39 — design-doc-refresh-and-p1-1-parameterization: Design docs (REQ-100, REQ-101): - hitl_matrix_design.md: 'dev-only spike'/'v1.2 wires the gates' framing replaced with v1.9 wired-gates reality; 8-concern matrix marked implemented (offline-testable subset + signed evidence artifacts, D-084); v1.9 wiring section cross-references hitl_gates.py + attestation_matrix.py; approver_dr noted. - audit_ledger_design.md: outbox marked shipped+production since v1.8; S3 Object Lock + JWS + async worker + DLQ + daily checkpoints clearly labeled 'Deferred to a future milestone (D-083)'; RPO/RTO table updated; approver fields note v1.9 hitl_gates.attest. P1-1 adapter parameterization (REQ-102, D-085): - ecs-service interface.json: desired_count (default 1), launch_type (FARGATE), family (app) inputs added. - alb interface.json: load_balancer_type (application), target_type (ip). - adapter.py: hardcoded defaults replaced with inputs.get(<name>, <default>); hardcoded 'acdl-microservice-rt'/'acdl-microservice-igw' Name tags derive from the VPC name input. - contract_resolver.py: child_input_map routes wires to the sub-resource that declares the input (desired_count → aws:ecs:service, family → aws:ecs:task_definition, target_type → targetgroup, etc.). - microservice composition.json: wires added for the new inputs. Tests: +21 (test_p1_1_adapter_parameterization.py, test_design_docs_current.py). 371 passed; run_ci.sh green; run_platform.sh --check-only green; v1.1 S3 regression preserved.
alb — Application Load Balancer (load balancer + target group + listener)
Module kind: primitive | Version: 1.0.0
An Application Load Balancer with a target group and a listener. This is
a multi-resource module: it creates a load balancer, a target group, and
a listener that forwards traffic to the target group. The target group
is what ecs-service registers its tasks with.
Resources
| Resource | Type | Purpose |
|---|---|---|
| load_balancer | aws_lb |
Application load balancer in the VPC subnets |
| target_group | aws_lb_target_group |
Target group for the ECS service tasks |
| listener | aws_lb_listener |
Listener forwarding the LB port to the target group |
Inputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
name |
string | yes | — | Name tag for the load balancer and child resources |
subnets |
string | yes | — | Comma-separated subnet ids (from vpc) |
security_group |
string | yes | — | Security group id for the load balancer |
port |
number | no | 80 | Listener port |
protocol |
string | no | HTTP |
Listener protocol |
region |
string | yes | — | AWS region the load balancer is created in |
Outputs
| Name | Type | Description |
|---|---|---|
lb_arn |
arn | The load balancer ARN |
listener_arn |
arn | The listener ARN |
target_group_arn |
arn | The target group ARN |
Usage
{
"id": "alb",
"type": "aws:elbv2:loadbalancer",
"module": "alb@1.0.0",
"inputs": {
"name": "acdl-microservice",
"subnets": "ref:vpc.subnet_ids",
"security_group": "ref:roles.role_arn",
"port": 8080,
"protocol": "HTTP",
"region": "us-east-1"
}
}
The target_group_arn output is referenced by ecs-service as its
lb_target_group_arn input to wire the service to the ALB.
Compliance extension points
- TLS / HTTPS listener — add
aws_acm_certificate+ssl_policy+certificate_arnfor encryption in transit (SOC2 CC6.1, PCI-DSS 4.1, HIPAA §164.312(e)(1), GDPR Art.32). - Access logs — add
access_logs { bucket = ..., prefix = ... }to the load balancer (SOX, SOC2 CC7.2, DORA ICT audit trail). - Security group rules — add ingress/egress rules restricting traffic to known sources (SOC2 CC6.6, PCI-DSS 1.2).
- Health check — add a
health_checkblock to the target group (SOC2 CC7.3 monitoring, DORA operational resilience). - WAF — add
aws_wafv2_web_acl_associationfor application-layer protection (SOC2 CC7.6, PCI-DSS 6.5, DORA ICT risk). - Deregistration delay — add
deregistration_delayfor graceful draining (SOC2 CC9.1 resilience).
Examples
Validated example contracts are in examples/. The platform-test
pipeline validates them against schemas/contract.schema.json.
Simple
A minimal deployment:
uses: acdl/pipelines/deploy.yaml@v1.6
module: alb
environment: dev
inputs:
name: my-alb
subnets: subnet-aaa,subnet-bbb
security_group: sg-xxx
port: 80
protocol: HTTP
region: us-east-1
Complex
A production deployment with optional inputs:
# Complex ALB with HTTPS + ACM cert (requires a consumer-supplied domain)
uses: acdl/pipelines/deploy.yaml@v1.6
module: alb
environment: dev
inputs:
name: my-production-alb
subnets: subnet-aaa,subnet-bbb
security_group: sg-xxx
port: 443
protocol: HTTPS
region: us-east-1
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.