Jon Chery
2682719f24
Presentation changes (both Marp decks + source markdown): 1. Title slide: deck title as H1 (slightly bigger), 'Agentic Cloud Delivery Platform' as H3 subtitle — cleaner title hierarchy 2. DX deck: removed Local Reproducibility slide (not beneficial for DX) 3. DX deck: Safe Promotion Path slide redesigned with side-by-side layout for Approaches A and B (HTML table, two columns) 4. DX deck: 'an agent' → 'an AI agent' (slide 2 + Citizen Developer slide) 5. DX deck: What a Developer Does — diagram floated to the right side 6. Header simplified to just the deck name (subtitle now on title slide) HIPAA removal (25 files): - Completely removed all HIPAA references from all markdown documentation, presentation source files, module READMEs, and rendered HTML - Removed HIPAA from compliance milestone lists (GDPR, SOX, SOC2, DORA remain) - Removed HIPAA section references (§164.xxx) from compliance annotations - Cleaned up empty parentheses and broken commas left by removal - Re-rendered both HTML decks from updated Marp source ---ci--- phase: 47 milestone: v1.9 status: complete requirements: covered: [] partial: [] ---/ci---
ecr — ECR repository
Module kind: primitive | Version: 1.0.0
A single ECR repository that hosts the container image for the ECS task. The simplest container-registry module — one resource, two inputs, two outputs.
Resources
| Resource | Type | Purpose |
|---|---|---|
| repository | aws_ecr_repository |
The ECR repository |
Inputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
name |
string | yes | — | The ECR repository name |
region |
string | yes | — | AWS region the repository is created in |
Outputs
| Name | Type | Description |
|---|---|---|
repository_url |
string | The ECR repository URL |
repository_arn |
arn | The ECR repository ARN |
Usage
{
"id": "ecr",
"type": "aws:ecr:repository",
"module": "ecr@1.0.0",
"inputs": {
"name": "acdl-microservice",
"region": "us-east-1"
}
}
The repository_url output is used to build the image input for
ecs-service (e.g. <repository_url>:latest).
Compliance extension points
- Image scanning — add
image_scanning_configuration { scan_on_push = true }for vulnerability scanning (SOC2 CC7.6, DORA ICT risk testing, security monitoring). - Encryption — add
encryption_configuration { encryption_type = "KMS", kms_key = ... }with a customer-managed key (SOC2 CC6.1, GDPR Art.32). - Image tag immutability — add
image_tag_mutability = "IMMUTABLE"to prevent tag overwriting (SOX §802, SOC2 CC6.1 integrity, DORA audit integrity). - Lifecycle policy — add
aws_ecr_lifecycle_policyto enforce image retention / cleanup (GDPR Art.5(2) data minimization, SOC2 CC5.2). - Access policy — add a repository policy restricting pull/push to known roles (SOC2 CC6.1.
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: ecr
environment: dev
inputs:
name: my-repo
region: us-east-1
Complex
A production deployment with optional inputs:
# Complex ECR with lifecycle policy + image scanning
uses: acdl/pipelines/deploy.yaml@v1.6
module: ecr
environment: dev
inputs:
name: my-production-repo
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.