Skip to main content
This guide produces the evidence required to say that Harmonia ran on AWS. A successful local build or emulator run is not cloud evidence.

​
Before recording

Use one dedicated AWS environment and one selected region. Enable AgentCore Memory, deploy both ECS Fargate services, and complete one real authorized Harmonia job. Use a fresh job identifier that can be followed across every surface. Prepare browser tabs for:
  1. the signed-in Harmonia dashboard at its HTTPS application URL;
  2. ECS Fargate services and revisions for harmonia-web and harmonia-agent;
  3. AgentCore Runtime execution or logs for the same job;
  4. AgentCore Memory showing a write from a verified outcome and a later retrieval in the same workspace/brand scope;
  5. SQS delivery and dead-letter metrics for the stage queue;
  6. the workspace-scoped DynamoDB job, events, approval, receipt, verification, and usage records;
  7. CloudWatch traces or the telemetry backend filtered to the job’s trace ID.
Redact customer content and account identifiers before recording. Do not open raw configuration or credential views.

​
Capture a resumable asynchronous run

Create a job from an authorized source and show its job ID. Let at least one SQS-driven stage complete, then display the persisted DynamoDB stage and event timestamp. Restart the private worker revision or allow a safe redelivery, and show the same job resuming from durable state without creating a duplicate external receipt. The proof is the correlation among the job ID, SQS delivery, DynamoDB state, AgentCore Runtime invocation, and idempotent receipt—not narration alone.

​
Capture cross-session memory

Complete a job through approval, independent verification, and learn. Show that AgentCore Memory receives only an eligible fact such as an operator decision or verified outcome under the job’s workspace and brand scope. Start a separate later job in the same workspace and show its fresh AgentCore Runtime invocation retrieving that fact. Then show a different workspace producing no retrieval for the same query. This demonstrates persistent cross-session context and tenant isolation. If the two jobs have not actually been separated by weeks, describe the architecture as week-capable; do not claim elapsed-time evidence that was not captured.

​
Capture the sovereignty and security boundary

Show the selected us-east-1 resources, exact Bedrock model/inference-profile IDs and their routing regions, AgentCore runtime/memory, source Knowledge Base, bucket and queue identifiers, and separate runtime roles. Cross-region inference profiles do not establish single-region data residency. ElevenLabs is an external music provider; disclose its processing separately. Show the human approval boundary and metadata-only traces without prompts, transcripts, drafts, or media content.

​
Completion criteria

The evidence is complete only when the video visibly includes:
  • a working HTTPS application URL;
  • both ECS Fargate services and their revisions;
  • one real AgentCore Runtime invocation;
  • one AgentCore Memory write and a later scoped retrieval;
  • SQS activity and durable DynamoDB state for the same job;
  • one approval receipt and independently verified outcome;
  • one correlated metadata-only trace;
  • matching regional locations and SQS storage policy.
Store full-resolution screenshots, command output, job IDs, trace IDs, revision names, timestamps, and the final video under the private agents-for-humans evidence directory. Until those artifacts exist, authenticated AWS execution remains unverified.
Last modified on September 14, 2026