AWS re:Invent 2021 - Integrate Amazon EKS with your networking pattern

Because of its security, reliability, and scalability capabilities, Amazon EKS is used by organizations in their most sensitive and mission-critical applications. This session focuses on how you can set up networking for Amazon EKS, connect it to Amazon VPC, and expose your Kubernetes application using Elastic Load Balancing and AWS App Mesh.
Learn more about re:Invent 2021 at bit.ly/3IvOLtK
Subscribe:
More AWS videos bit.ly/2O3zS75
More AWS events videos bit.ly/316g9t4
ABOUT AWS
Amazon Web Services (AWS) hosts events, both online and in-person, bringing the cloud computing community together to connect, collaborate, and learn from AWS experts.
AWS is the world’s most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Millions of customers-including the fastest-growing startups, largest enterprises, and leading government agencies-are using AWS to lower costs, become more agile, and innovate faster.
#AWS #AmazonWebServices #CloudComputing

[@chetanagrawal492]

One of the best videos out there on Amazon EKS networking !!

[@CarlosSantanaDev]

Great content on EKS networking options, so far best video I have found 🎉

[@srirajan1933]

Echoing others' comments below; great work (as usual) Tom and Theo! During t=19:10 to 21:10, the key difference in the 2 scenarios is the location of the Worker node -- Public Subnet as in the first case (Source NAT enabled, _EXTERNALSNAT=false) where the NAT Gateway is bypassed and goes directly to IGW because it already has route to Internet (it's in the Public subnet with such a route), and Private Subnet as in the 2nd case (Source NAT disabled, _EXTERNALSNAT=true) where the NAT Gateway performs the necessary translation (or NAT64 if it's an IPv6 address) before advertising to IGW and onward to the Internet. Tom did explain this, but the slide transition was fast so I missed this initially; this nuance helped me understand the two use-cases; it may help others too.

[@abhinavkapoor321]

Awesome !! Certainly one of the best content on the subject

[@aegisbgk]

Kudos to both architects

[@ethramkumar]

Loved the presentation and ease of explanation!👍

[@AlexLi-zige]

great talk, thansk

[@darrenlin5996]

Super good presentation!

[@amjads8971]

so prefix solution is only supported on nitro instance types , which is again not good.

[@yangzhihong521]

非常好👍