AWS has published a reference architecture for “ambient” agents that begin work when software events occur rather than waiting for a person to open a chat. An uploaded file, scheduled task or monitoring signal can create a job in Amazon Bedrock AgentCore, where an agent processes it and requests human input before a consequential step.
The sample connects Amazon S3 event notifications to Lambda functions, an SQS work queue and DynamoDB state. AgentCore Runtime hosts the agent in an isolated container, while a React interface shows pending, interrupted, completed and failed jobs. A single ask_human tool handles clarification, review and approval requests, allowing a paused session to continue after a person responds.
Teams can configure a signal to wait for manual review before execution or run automatically and interrupt a person only when the agent asks. S3 uploads and scheduled jobs are included. Webhooks and database-change triggers are described as extension points that require additional handlers.
This is a deployable sample, not a fully managed switch for every event source. It requires an AWS account, infrastructure permissions, container tooling and access to a supported Bedrock model. The example also caps each agent turn at Lambda’s 15-minute limit. Production users still need to define permissions, idempotency, retry behavior and which actions always require approval.