New serverless pattern - lambda-microvms-multi-tenant-ai-agents#3215
Open
hustshawn wants to merge 1 commit into
Open
New serverless pattern - lambda-microvms-multi-tenant-ai-agents#3215hustshawn wants to merge 1 commit into
hustshawn wants to merge 1 commit into
Conversation
7c30c9b to
68404c3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
This pattern runs a self-hosted AI agent one isolated Lambda MicroVM per tenant: per-tenant state persisted on Amazon EFS, Amazon Bedrock via a VPC endpoint, and an orchestrator Lambda (API Gateway + DynamoDB registry + EventBridge sweeper) that cold-starts, resumes, and reaps tenant VMs on demand. The MicroVM image and VPC egress connector are declared natively in CloudFormation (AWS::Lambda::MicrovmImage / AWS::Lambda::NetworkConnector); deploy is a single script. Includes an optional Telegram push front-end per tenant.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.