Files
acdl/modules/l1/kms-key
Jon Chery 0ca383dae6 feat(P4): transparent terraform + feature flags + run_platform.sh split (REQ-233..238)
Create run_codegen.sh (pre-TF: env check, validate, resolve, adapt).
Create run_postapply.sh (post-TF: Checkov, confidence, HITL, outbox, SSM, uptime).
Add variable 'enabled' (bool, default true) + count=var.enabled?1:0 to all 12
L1 modules (alb, cloudfront, ecr, ecs-cluster, ecs-service, iam-role, kms-key,
rds, s3, uptime, vpc, waf). Fix all cross-resource references with [0] indexing.
Update interface.json for all modules to declare 'enabled' input.
Fix stale artifact path /tmp/acdl_platform_run_v18 → /tmp/nova_platform_run (REQ-238).
run_platform.sh remains as backward-compat shim for local-dev usage.

---ci---
project: acdl
phase: 4
milestone: v1.20
status: execute
requirements: [REQ-233, REQ-234, REQ-235, REQ-236, REQ-237, REQ-238]
---/ci---
2026-08-07 18:49:56 +00:00
..

kms-key — KMS customer-managed key

Module kind: primitive | Version: 1.0.0

A customer-managed KMS key for per-stack encryption. Created with key rotation enabled. One key per L2 deployment (no shared keys).

Resources

Resource Type Purpose
kms-key aws_kms_key The KMS customer-managed key

Inputs

Name Type Required Default Description
description string yes Description of the KMS key
region string yes AWS region the KMS key is created in
deletion_window_days number no 30 Number of days before the key is deleted after deletion is requested

Outputs

Name Type Description
kms_key_arn arn The ARN of the KMS key
kms_key_id string The ID of the KMS key

NFRs

Name Type Default Description
enable_rotation boolean true Enable automatic key rotation
deletion_protection boolean true Prevent key destruction
encryption_enabled boolean true Encryption is always enabled for a KMS key

Usage

{
  "id": "kms-key",
  "type": "aws:kms:key",
  "module": "kms-key@1.0.0",
  "inputs": {
    "description": "Nova per-stack CMK",
    "region": "us-east-1"
  }
}

A concrete instance is at instance.json (used by the platform pipeline as the regression baseline).

Compliance extension points

  • Key rotation — automatic key rotation enabled by default (SOC2 CC6.1, GDPR Art.32).
  • Deletion protection — pending deletion window prevents accidental destruction (SOC2 CC7.2).
  • Key policy — restrict key usage to the stack's IAM roles (SOC2 CC6.1, GDPR Art.32).
  • Audit logging — CloudTrail logs all KMS API calls (SOC2 CC7.2, DORA audit trail).

Examples

Validated example contracts are in examples/. The platform-test pipeline validates them against schemas/contract.schema.json.

Simple

A minimal deployment:

examples/simple.yml

environment: dev
id: kms
infrastructure:
  kms-key:
    inputs:
      description: Simple CMK for testing
      region: us-east-1
    version: 1.0.0
name: kms-key

Complex

A production deployment with optional inputs:

examples/complex.yml

environment: dev
id: kms
infrastructure:
  kms-key:
    inputs:
      deletion_window_days: 90
      description: Production CMK with 90-day deletion window
      region: us-east-1
    version: 1.0.0
name: kms-key

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.