[{"data":1,"prerenderedAt":48},["ShallowReactive",2],{"repo-sample-lambda-microvm-claude-managed-agents":3},{"id":4,"title":5,"contributors":6,"date":10,"description":11,"diagram":12,"extension":13,"framework":14,"gitHub":16,"introBox":19,"language":24,"meta":27,"resources":28,"services":37,"simplicity":43,"stem":44,"type":45,"usecase":46,"__hash__":47},"repos\u002Frepos\u002Fsample-lambda-microvm-claude-managed-agents.json","Claude Managed Agents on AWS Lambda MicroVMs",[7,8,9],"content\u002Fcontributors\u002Fjosh-rodgers.json","content\u002Fcontributors\u002Fdavid-lamb.json","content\u002Fcontributors\u002Fben-freiberg.json","2026-07-14","A reference solution that runs Claude's self-hosted sandbox tool execution on AWS Lambda MicroVMs, launching a fresh, VM-isolated MicroVM per Claude session. This allows your agents to access resources through your AWS environment without exposing connectivity, while you retain full monitoring and governance over those resources.","\u002Fassets\u002Fimages\u002Frepos\u002Fsample-lambda-microvm-claude-managed-agents.png","json",[15],"AWS SAM",{"template":17},{"repoURL":18},"https:\u002F\u002Fgithub.com\u002Faws-samples\u002Fsample-lambda-microvm-claude-managed-agents",{"headline":5,"text":20},[21,22,23],"This reference solution demonstrates how to run Claude's self-hosted sandbox tool execution on AWS Lambda MicroVMs. It implements an orchestrator plus ephemeral-MicroVM-per-session pattern, where each Claude session gets its own Firecracker-isolated compute environment with VM-level isolation and no state shared between sessions.","The control plane is webhook-driven. When a Claude session starts, Anthropic sends a webhook to an Amazon API Gateway endpoint (protected by AWS WAF) that triggers a Lambda launcher. The launcher verifies the signature using a secret from Systems Manager Parameter Store and launches a single MicroVM. The MicroVM fetches per-session credentials, claims the session, executes tools, and posts results back.","The security model keeps organization API keys away from AWS compute. Only per-session references and environment-key parameter names are forwarded, secrets live in Parameter Store, and IAM execution roles enforce least-privilege access. The event-driven design launches fresh MicroVMs on demand, so agents can run untrusted code in strong isolation while preserving full organizational governance and CloudWatch monitoring.",[25,26],"Python","Node.js",{},{"headline":29,"bullets":30},"Additional resources",[31,34],{"text":32,"link":33},"AWS Lambda MicroVMs Documentation","https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Flambda-microvms.html",{"text":35,"link":36},"Firecracker - Secure and fast microVMs for serverless computing","https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fopensource\u002Ffirecracker-open-source-secure-fast-microvm-serverless\u002F",[38,39,40,41,42],"lambda-event-functions","apigw","s3","ssm","iam","400","repos\u002Fsample-lambda-microvm-claude-managed-agents","Application","AI\u002FML\u002FGenAI","9rbj6RwVKs1AHcytzrmhat7ffOKWlZEdBSI54TxyBxs",1792578865018]