Cloud extractor — AWS resources to ArchiMate Technology layer

[victorsoriadrp]

Context

A common source of architecture decay is the gap between "what we documented" and "what's actually running in the cloud." An AWS extractor closes that loop by reflecting real infrastructure as ArchiMate Technology elements.

Scope

• Authenticate via AWS SDK (IAM role / access key — configurable)
• Discover resources: EC2 instances, ECS services, EKS clusters, RDS, S3 buckets, Lambda functions, API Gateway, ELBs, VPCs
• Map each to an ArchiMate Technology element (Node, SystemSoftware, TechnologyService, etc.) with consistent ID derived from ARN
• Express relationships (e.g., Lambda → API Gateway = Composition)
• Idempotent re-runs: update existing elements, mark removed ones, never duplicate

Acceptance criteria

• CLI command: archipulse extract aws --workspace <id> [--region <r>]
• MCP tool: extract_aws_resources (with same options)
• Configurable scope (account, region, resource types)
• Snapshot taken before import for rollback
• Documented in extractor docs (linked to Documentation site — architecture, deployment, API and MCP reference #92)