Files

T

Jon Chery 895a2f3806 docs(P20): specify phase 20 — consumer happy path + reusable deploy workflow (v1.5)

---ci---
project: acdl
phase: 20
milestone: v1.5
status: specify
---/ci---

Add v1.5 milestone to ROADMAP.md + REQUIREMENTS.md. Phase 20 covers
REQ-46 (README consumer model + mermaid + L3B/spike scrub), REQ-47
(generic CONSUMER_GUIDE.md + versioned uses: + consumer-scoped prereqs
+ run-time platform fetch), REQ-48 (zero-trust OIDC/ABAC credentials +
static-key override + daily rotation), REQ-49 (reusable byte-identical
deploy.yml Gitea+GitHub implementing pipelines/deploy.yaml), REQ-50
(contracts/static-asset.yaml @v1.4), REQ-51 (deploy-workflow conformance
tests). Update config.json milestone to v1.5.

2026-07-22 17:09:23 +00:00

interface.json

docs(P20): specify phase 20 — consumer happy path + reusable deploy workflow (v1.5)

2026-07-22 17:09:23 +00:00

README.md

docs(P20): specify phase 20 — consumer happy path + reusable deploy workflow (v1.5)

2026-07-22 17:09:23 +00:00

README.md

l1-iam-role — IAM role

Module kind: L1 primitive | Version: 1.0.0

A single IAM role with an assume-role policy and optional managed policy attachments. Used as the ECS task execution role.

Resources

Resource	Type	Purpose
role	`aws_iam_role`	The IAM role with assume-role policy

Inputs

Name	Type	Required	Default	Description
`role_name`	string	yes	—	The IAM role name
`assume_role_policy`	string	yes	—	Assume-role policy document (JSON string)
`managed_policies`	string	no	—	Comma-separated list of managed policy ARNs to attach
`region`	string	yes	—	AWS region the role is created in

Outputs

Name	Type	Description
`role_arn`	arn	The IAM role ARN
`role_id`	string	The IAM role id

Usage

{
  "id": "roles",
  "type": "aws:iam:role",
  "module": "l1-iam-role@1.0.0",
  "inputs": {
    "role_name": "acdl-microservice-exec",
    "assume_role_policy": "{\"Version\":\"2012-10-17\",\"Statement\":[{\"Effect\":\"Allow\",\"Principal\":{\"Service\":\"ecs-tasks.amazonaws.com\"},\"Action\":\"sts:AssumeRole\"}]}",
    "managed_policies": "arn:aws:iam::aws:policy/service-role/AmazonECSTaskExecutionRolePolicy",
    "region": "us-east-1"
  }
}

The assume_role_policy is a JSON string — the adapter jsonencodes it into the Terraform assume_role_policy argument. The managed_policies input is a comma-separated list of ARNs, emitted as managed_policy_arns = [...].

Compliance extension points

Permissions boundary — add permissions_boundary to enforce least-privilege guardrails (SOC2 CC6.1, SOX ITGC, DORA ICT access control).
Inline policy — add aws_iam_role_policy for fine-grained least-privilege instead of broad managed policies (SOC2 CC6.1, HIPAA §164.308(a)(4)).
MFA conditions — add condition blocks requiring MFA for assume-role (SOC2 CC6.1, HIPAA §164.312(d)).
Source IP / region conditions — add aws:SourceIp / aws:RequestedRegion conditions for data residency enforcement (GDPR Art.44-49, DORA ICT third-party risk).
Access Analyzer — add aws_accessanalyzer_analyzer to verify least-privilege (SOC2 CC6.1, GDPR Art.32).
Role separation — add a separate task role vs. execution role (SOC2 CC6.3 segregation of duties).

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.