How Harmonia uses it
CDK creates separate web, worker, scanner, AgentCore Runtime, Gateway, Knowledge Base, and scheduler roles. Web and worker access the native state table and scoped asset bucket. The worker consumes SQS; EventBridge can send only to its configured control queue. The scanner is reachable only from the web service. AgentCore cognition calls the private web service with a server-side token and accesses only its configured memory, research, and model resources.
Security and authority
IAM permits infrastructure calls; it cannot grant workspace membership, source rights, approvals, or effect authority. Strongly consistent application reads, scoped service headers, current digests, budgets, and durable claims remain mandatory. Public ingress rejects internal API paths.
Failure behavior
Missing permissions fail visibly. Deployment wrappers require a spending authorization, and CDK IAM broadening remains reviewable. Service tokens and encryption keys come from Secrets Manager.
Evidence status
Local synthesis validates the declared topology. Actual service startup, IAM access, and cross-tenant denial require authenticated rehearsal. No deployed policy inspection is claimed.
Relevant files
infra/aws/stack.tssrc/lib/internalAuth.tsagent/harmonia_agent/main.py
Last modified on September 14, 2026
