Strobe Assistant AWS architecture The browser reaches the ACP service on ECS through a public load balancer. ACP calls Bedrock Gemma and reaches the MCP service through an internal load balancer. MCP reads DynamoDB and S3 Vectors and calls the Strobe API. Uploads go to S3, then EventBridge, SQS and a classifier Lambda that writes DynamoDB. A DynamoDB stream triggers an embedding Lambda that updates S3 Vectors. A scheduled heartbeat Lambda reads posts and writes run records. AWS, ap-southeast-2 Strobe userbrowser Strobe APIAssessment 1 VPC, ECS Fargate Public ALBHTTPS, WSS, ACM ACP serviceWebUI + relay Internal ALBprivate /mcp MCP servicetools, own task Amazon Bedrock Gemma 3 12Bchat, vision, recaps Titan embed v2text to vectors Data DynamoDBA2: images, chunks, runsStrobe: users, posts, comments S3 Vectorscaptions index Event-driven, serverless S3 mediaphoto bucket EventBridgeobject created SQS queue+ dead-letter Classifier λlabels images Heartbeat λScheduler, daily Embedding λre-indexes Shared by every service Cognito Secrets Manager Parameter Store CloudWatch Logs ECR uploads stream Ask Upload Every morning calls Bedrock outside AWS