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---
90 lines
2.3 KiB
Markdown
90 lines
2.3 KiB
Markdown
# ecs-cluster — ECS Fargate cluster
|
|
|
|
> **Module kind:** primitive | **Version:** 1.0.0
|
|
|
|
An ECS Fargate cluster. The simplest ECS module — one resource, two
|
|
inputs, two outputs. The cluster is the container orchestration
|
|
boundary that `ecs-service` references for task placement.
|
|
|
|
## Resources
|
|
|
|
| Resource | Type | Purpose |
|
|
|----------|------|---------|
|
|
| cluster | `aws_ecs_cluster` | The ECS Fargate cluster |
|
|
|
|
## Inputs
|
|
|
|
| Name | Type | Required | Default | Description |
|
|
|------|------|----------|---------|-------------|
|
|
| `name` | string | yes | — | The ECS cluster name |
|
|
| `region` | string | yes | — | AWS region the cluster is created in |
|
|
|
|
## Outputs
|
|
|
|
| Name | Type | Description |
|
|
|------|------|-------------|
|
|
| `cluster_arn` | arn | The ECS cluster ARN |
|
|
| `cluster_id` | string | The ECS cluster id (name) |
|
|
|
|
## Usage
|
|
|
|
```json
|
|
{
|
|
"id": "cluster",
|
|
"type": "aws:ecs:cluster",
|
|
"module": "ecs-cluster@1.0.0",
|
|
"inputs": {
|
|
"name": "acdl-microservice",
|
|
"region": "us-east-1"
|
|
}
|
|
}
|
|
```
|
|
|
|
The `cluster_arn` output is referenced by `ecs-service` as its
|
|
`cluster_arn` input.
|
|
|
|
## Compliance extension points
|
|
|
|
- **Container Insights** — add `configuration { container_insights = "enabled" }` for observability (SOC2 CC7.3, DORA ICT risk monitoring).
|
|
- **CloudWatch Logs** — add a log group with retention policy for cluster-level audit logs (SOX, SOC2 CC7.2.
|
|
- **Encryption** — add `settings { name = "containerInsights", value = "enabled" }` and KMS-based encryption for container data (GDPR Art.32).
|
|
|
|
## Examples
|
|
|
|
Validated example contracts are in [`examples/`](examples/). The platform-test
|
|
pipeline validates them against `schemas/contract.schema.json`.
|
|
|
|
### Simple
|
|
|
|
A minimal deployment:
|
|
|
|
[`examples/simple.yaml`](examples/simple.yaml)
|
|
```yaml
|
|
uses: acdl/pipelines/deploy.yaml@v1.6
|
|
module: ecs-cluster
|
|
environment: dev
|
|
inputs:
|
|
name: my-cluster
|
|
region: us-east-1
|
|
```
|
|
|
|
### Complex
|
|
|
|
A production deployment with optional inputs:
|
|
|
|
[`examples/complex.yaml`](examples/complex.yaml)
|
|
```yaml
|
|
# Complex ECS cluster with container insights
|
|
uses: acdl/pipelines/deploy.yaml@v1.6
|
|
module: ecs-cluster
|
|
environment: dev
|
|
inputs:
|
|
name: my-production-cluster
|
|
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. |