Two architectural changes: 1. Created terraform/ci-vpc/ — a short-lived VPC for L1 module lifecycle testing, separate from the long-lived platform VPC. Created before VPC-dependent modules (alb, ecs-service, rds, uptime) are tested, destroyed after. Outputs (vpc_id, subnet_ids, sg_id, cluster_arn) are passed to those modules via scripts/run_lifecycle_test.sh + run_lifecycle_destroy.sh wrappers that inject the CI VPC outputs into the example contracts. 2. Updated the workflow to use ci-vpc-apply → lifecycle (with artifact passing) → ci-vpc-destroy (always runs). 8 module-specific fixes: - s3: unique bucket names (acdl-ci-s3a-simple/complex) instead of globally-taken 'my-simple-bucket' - kms-key: alias name with no spaces (locals.tf → alias/acdl-ci-kms) - iam-role: example contract uses role_name (not name, which the interface doesn't declare) - ecs-service: example contract uses family (not name); VPC inputs (cluster_arn, subnets, security_group) injected by CI VPC wrapper - uptime: added subnets, security_group, cluster_arn to interface + module; network_configuration is dynamic (only when subnets provided) - rds: added subnet_ids input + db_subnet_group resource (conditional on subnet_ids being non-empty) - alb: removed hardcoded placeholder sg/subnet values from examples; vpc_id + subnets + security_group injected by CI VPC wrapper - cloudfront: removed invalid placeholder WAF ARN from complex example Regression: 479 passed, 0 skipped, 5 deselected. All 24 example contracts pass --check-only. ---ci--- project: acdl phase: P59 milestone: v1.11 status: execute ---/ci---
rds — RDS database instance
Module kind: primitive | Version: 1.0.0
An RDS database instance. Supports multiple database engines (postgres,
mysql, mariadb, sqlserver, oracle) via the engine input. The adapter
translates the engine-agnostic aws:rds:instance stack type to the
Terraform aws_db_instance resource.
Resources
| Resource | Type | Purpose |
|---|---|---|
rds |
aws_db_instance |
The RDS database instance |
Inputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
engine |
string | yes | — | Database engine (postgres, mysql, mariadb, sqlserver-ex, sqlserver-web, sqlserver-se, oracle-se2) |
engine_version |
string | yes | — | Engine version (e.g. 16.4 for postgres, 8.4 for mysql) |
instance_class |
string | yes | db.t3.micro |
RDS instance class (e.g. db.t3.micro, db.r6g.large) |
allocated_storage |
number | no | 20 | Allocated storage in GB |
db_name |
string | yes | — | The database name (some engines have restrictions) |
username |
string | yes | — | Master username |
multi_az |
boolean | no | false | Multi-AZ deployment |
storage_encrypted |
boolean | no | true | Enable storage encryption |
region |
string | yes | — | AWS region the RDS instance is created in |
Outputs
| Name | Type | Description |
|---|---|---|
db_endpoint |
string | The RDS instance endpoint (host:port) |
db_arn |
arn | The RDS instance ARN |
NFRs
| Name | Type | Default | Description |
|---|---|---|---|
backup_retention_period |
number | 7 | Backup retention period in days |
deletion_protection |
boolean | true | Enable deletion protection (default true for prod) |
Usage
{
"id": "rds",
"type": "aws:rds:instance",
"module": "rds@1.0.0",
"inputs": {
"engine": "postgres",
"engine_version": "16.4",
"instance_class": "db.t3.micro",
"allocated_storage": 20,
"db_name": "acdl_db",
"username": "acdl_admin",
"multi_az": false,
"storage_encrypted": true,
"region": "us-east-1"
},
"nfrs": {
"backup_retention_period": 7,
"deletion_protection": true
}
}
A concrete instance is at instance.json (used by the platform pipeline
as the regression baseline).
Compliance extension points
- KMS encryption — add a customer-managed KMS key for storage
encryption (
kms_key_idargument) (SOC2 CC6.1, GDPR Art.32). - Automated backups — the
backup_retention_periodNFR controls automated backup retention; extend with backup windows + copy tags to another region for DR (SOX ITGC, DORA operational resilience). - Audit logging via CloudTrail — RDS does not emit CloudTrail events
for data-plane access; add
aws_db_instance_automated_backups_replication- CloudWatch Logs for database audit (SOX, SOC2 CC7.2).
- IAM database authentication — add
iam_database_authentication_enabled = trueso IAM users/roles can authenticate to the database without long-lived passwords (SOC2 CC6.1). - Read replicas — add
aws_db_instancewithreplicate_source_dbfor read scaling and DR failover (SOC2 CC9.1, DORA operational resilience).
Examples
Validated example contracts are in examples/. The platform-test
pipeline validates them against schemas/contract.schema.json.
Simple
A minimal deployment:
environment: dev
id: rds
infrastructure:
rds:
inputs:
allocated_storage: 20
db_name: my_app_db
engine: postgres
engine_version: '16.4'
instance_class: db.t3.micro
region: us-east-1
username: db_admin
version: 1.0.0
name: rds-instance
Complex
A production deployment with optional inputs:
environment: dev
id: rds
infrastructure:
rds:
inputs:
allocated_storage: 100
db_name: my_production_db
engine: postgres
engine_version: '16.4'
instance_class: db.r6g.large
multi_az: true
region: us-east-1
storage_encrypted: true
username: db_admin
version: 1.0.0
name: rds-instance
Multi-engine variation
RDS supports multiple database engines. The engine input selects the engine;
the engine_version must match.
PostgreSQL
examples/simple.yml — postgres 16.4
MySQL
examples/mysql.yml — mysql 8.4
environment: dev
id: rds
infrastructure:
rds:
inputs:
allocated_storage: 20
db_name: my_mysql_db
engine: mysql
engine_version: '8.4'
instance_class: db.t3.micro
region: us-east-1
username: db_admin
version: 1.0.0
name: rds-instance
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.