AWS/GitHub/sample-e2b-on-aws

• aws-samples/sample-e2b-on-aws

  • AWS Samples repository that deploys E2B AI sandboxes into a customer’s own AWS account using CloudFormation (new or existing VPC), optional Grafana/PostHog, bastion access, Nomad-oriented deployment flow, and post‑deploy steps (ACM DNS, wildcard to ALB, template creation scripts, sandbox API calls). Licensed Apache‑2.0.
    • aws-samples/sample-e2b-on-aws
    • English README documents prerequisites (AWS account, owned domain, optional observability accounts), security checklist (RDS backups, IMDSv2, logging, multi‑AZ, etc.), two templates (e2b-setup-env.yml, e2b-setup-env-existing-vpc.yml—existing VPC notes Aurora Serverless PostgreSQL and Redis Serverless), E2B CLI usage against your domain, SDK cookbook clone flow, troubleshooting (Nomad eligibility, ECR pull auth), and cleanup (Terraform destroy, CFN stack delete, manual S3/ALB checks).
  • Upstream note (from README): built from a pinned e2b-dev/infra commit; suggests verifying compatibility if upgrading.
  • Why this matters next to e2b: It is reference IaC, not a separate product—E2B’s software running on your AWS footprint, which is the clearest bridge between “E2B the agent cloud” and “AWS compute/network/data services you operate.”
  • Vs AWS/Lightsail / AWS/ECS/Express Mode: This repo is not an alternative to Lightsail or Express Mode; it consumes lower‑level AWS building blocks (VPC, EC2, ALB, RDS, ECR, S3, etc.) to stand up E2B‑style sandbox infrastructure. Lightsail and Express Mode address different mainstream AWS journeys (simple VPS / simplified ECS services) without implementing E2B’s sandbox control plane unless you build it yourself.