Jon Chery
3508671377
The L2 thin-composition layer (composition.json + contract_resolver.py + contract schema + sample contracts) has been removed completely. The implementation was unsatisfactory and is deferred for a later redesign. - Delete: composition.json x2, contract_resolver.py, contracts/ x2, contract.schema.json - Patch: run_platform.sh now loads a pre-existing IR instance instead of resolving a contract (the downstream adapter/checkov/confidence/outbox pipeline is unchanged) - Prune: L2 entries removed from registry.json (L1 entries unchanged) - Rewrite: all 7 L1 module READMEs in plain language (no jargon), each with Resources/Inputs/Outputs/Usage/Compliance-extension-points/Versioning sections derived from interface.json - Add: 2 L2 placeholder READMEs noting the composition is under redesign - Add: modules-ir/README.md catalog index + README-TEMPLATE.md ---ci--- project: acdl phase: 17 milestone: v1.3 status: execute ---/ci---
71 lines
2.9 KiB
Markdown
71 lines
2.9 KiB
Markdown
# l1-alb — Application Load Balancer (load balancer + target group + listener)
|
|
|
|
> **Module kind:** L1 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 `l1-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 `l1-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
|
|
|
|
```json
|
|
{
|
|
"id": "alb",
|
|
"type": "aws:elbv2:loadbalancer",
|
|
"module": "l1-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 `l1-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_arn` for 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_check` block to the target group (SOC2 CC7.3 monitoring, DORA operational resilience).
|
|
- **WAF** — add `aws_wafv2_web_acl_association` for application-layer protection (SOC2 CC7.6, PCI-DSS 6.5, DORA ICT risk).
|
|
- **Deregistration delay** — add `deregistration_delay` for graceful draining (SOC2 CC9.1 resilience).
|
|
|
|
## 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. |