9 requirements implemented across presentation decks and project docs: 1. DX closing slide: added 'Infrastructure as a utility, not a craft' bullet to convey the full vision (infrastructure consumed, not maintained; platform compounds value over time). 2. PW Problem slide: 'moving a merged change' → 'promoting a change'. 3. PW Problem slide: added 'Red tape' and 'Scalability without increasing headcount' bullets (4 frictions, not 2). 4. PW Roadmap slide: redesigned with side-by-side HTML table layout (Testing | Planned), 16px font, no overflow. 5. PW deck: added new slide 'What This Platform Is — and Isn't' after North Star (sovereign boundary, infrastructure as utility, 4 anti-goals). PW deck now 16 slides (was 15). 6. Maturity nomenclature: 'Available today'/'shipped' → 'Testing' across both decks + source markdown. New .testing badge (blue/teal #DBEAFE). Roadmap title: 'Testing vs. Planned'. The platform has 0 consumer adoption — 'shipped' was inaccurate. 7. Global: 'substrate' → 'engine' across entire project (88 matches, 30+ files including .ciagent/, docs/, modules/, adapters/, schemas/, code). 8. Presentation files only: 'forge' → 'VCS' / 'version control system' (6 occurrences in 4 files). 'forge' retained in all technical docs and code as the industry-standard term. 9. New .agentic badge (purple/violet #EDE9FE) appended to agentic features in both decks: confidence signal, autonomous dev, pattern recognition, dynamic module creation, citizen developer surface, auto-promotion. Also: Change Request ID format changed from 'CR-2026-001' to 'CHG0678912' across presentation files, consumer guide, and test fixtures. HTML re-rendered. PPTX rendered for release upload. ---ci--- phase: 48 milestone: v1.9 status: complete requirements: covered: [] partial: [] ---/ci---
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, 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.