Dedicated Infrastructure in a Multitenant World
summary
Adobe Experience Manager Cloud Service runs multitenant clusters but gives customers dedicated egress IPs and private links by pairing a per-tenant virtual network with an auto-scale set of VMs running Envoy plus an Envoy sidecar in each pod, tunneling traffic over HTTP/2 with mutual TLS. Configuration supports any protocol, gives dedicated public and private IPs, and is provisioned with Terraform/Terragrunt; certificate rotation and non‑overlapping IP ranges require extra operational work but the solution is deployed and working in production.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:42What is Adobe Experience Manager
- 1:32Adobe Experience Manager Cloud
- 2:19Security
- 2:37namespaces
- 3:15requirements
- 4:51first version
- 5:11how it works
- 8:31what is good
- 8:48what is bad
- 10:06Envoy
- 10:29Envoy Architecture
- 16:40VPN Private Connections
- 17:51Envoy envy configuration
- 20:48Code examples
- 21:36Cluster configuration
- 22:03Transport circuit configuration
- 22:39VM configuration
- 22:57Dynamic Forward Proxy
- 23:13Listener
- 23:24Connection Manager
- 26:14Forward Proxy
- 26:32Resources
- 26:55Debugging
- 28:15Conclusion
related talks
39mLessons Learned Migrating an Existing Product to a Multi Tenant Cloud Native Environment
05mLightning Talk: What Makes a Good Multi-tenant Kubernetes Solution?
26mMulti-Tenant vs Micro-Clusters in Kubernetes-Driven Platform Engineering
25mThe Cloud Native Journey at Adobe
31munlighted, but what about Security and Multi tenancy?
01h 00mArchitecting multi-tenant PaaS offerings
39mDesigning & Securing Multi-Tenant Runtime Environment at the New York Times
39mOptimizing Resource Usage in Kubernetes