Why should Amazon EKS microservices care about networking
summary
Examines how modern networking for Amazon EKS microservices moves beyond L3 connectivity to L7 “application networking,” specifically covering AWS services and patterns for service-to-service discovery and communication including Amazon VPC Lattice. Explains how pushing authentication, authorization, encryption and retry logic into the networking layer can offload those concerns from containerized applications and reviews concrete connectivity patterns for microservices on EKS.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:53This session (is opinionated...)
- 2:50Application networking, TL;DR
- 3:59Building blocks for application networking
- 7:26Where is my service? Client-Side
- 8:13Where is my service? Server-Side
- 14:52Pattern Summary
- 17:13Traffic Multiplier
- 19:01Sidecar proxies - East West
- 19:32Multi-Cluster Multi-Mesh?
- 20:08Multi-Cluster service mesh, LinkerD
- 23:32When your system evolves...
- 24:33Persona problem...
- 33:06Kubernetes Use Cases for Amazon VPC Lattice
- 35:02Use Case: Traffic Management
- 37:21Secure Access: Network layer controls
- 38:06Secure Access: Application layer controls
- 40:03Native K8s Integration with Amazon VPC Lattice
- 41:35Gateway API: Routes
- 42:08"Pattern" Summary
- 44:33Key Takeaways
related talks
18mGetting started with AWS AppMesh
34mLow Latency Multi-cluster Kubernetes Networking in AWS
05mModern Telco Applications
34mAWS Networking Fundamentals
40mCloud, Kubernetes, and Service Networking - Taming the Turtles
27mMicroservices: Awareness and Discovery Pattern on K8s
01h 04mnetworking fundamentals: Set up your global network
35mNetworking fundamentals on AWS