AWS re:Invent 2018: Extending Data Centers to Cloud: Connectivity Options & Best Practices NET302

Many enterprises on their journey to the cloud require consistent and highly secure connectivity between their existing data center and AWS footprints. In this session, we walk through the different architecture options for establishing this connectivity using AWS Direct Connect and VPN. With each option, we evaluate the considerations and discuss risk, performance, high availability, encryption, and cost. As we walk through these options, we discuss the associated best practices and answer some of the common questions that arise from enterprises that tackle design and implementation. Learn how to make connectivity decisions that are suitable for your workloads and how to best prepare against business impact in the event of failure. Complete Title: AWS re:Invent 2018: Extending Data Centers to the Cloud: Connectivity Options & Best Practices (NET302)

[@GauravSingh-ov9mh]

This is the best video on RUclips for all aws VPC and VPN connections.

[@chetanagrawal492]

Amazingly consolidated all connectivity options together while maintaining the clear distinction on which option to be used in which situation with to-the-point explanation. I think this video stands out over all other networking videos out there from Re:Invent sessions. Loved all the diagrams as well. Great stuff!!

[@cvcgen6224]

Awesome session! Lot of info in simple terms. No wonder its the Author of AWS Networking study guide

[@ckenox]

very fluent and amazing, tks for make public this material and congrats, your explanation is very clear...

[@abhashrimal9627]

Excellent session, very simple and clear way to explain the networking concepts.

[@madhukarpandey999]

Too good Sidharth, very well explained

[@nimishaabraham720]

thanks for the session, Sid! Simple, yet detailed explanation. just what i was looking for to understand connectivity options

[@safakenesyilmazer9255]

This is a great session, really comprehensive! Thanks

[@anjalivas1111]

Loved the Quiz at the end and the appropriate advice given when handing out prizes 😂

[@idkwutnametouse]

Excellent session. Thanks.

[@38khampha]

great session, learning a lot information for networking on aws

[@Rahul-oj9kq]

Thank you very much. Great presentation and content 👍

[@deepakgeorge010]

Very useful information. Articulated really well.

[@venkateshr9588]

45:40 Transit Gateway - I doubt it allows connecting Two VPC's with overlapping CIDR ranges. Per FAQ, it says not possible. Thoughts ?

[@bhomiktakhar8226]

nicely explained .

[@HambaAllah-xn2zp]

Thank you for the session

[@avinashshankarpalli2130]

Awesome session

[@ibmuser13]

Good one, thanks!

[@alexshlyonov6250]

Thank You

[@anjalivas1111]

Great talk

[@D35TR00]

Sounds like Transit VPC via CSRs is still the way to go since it offers way more flexibility and the cost of the BYOL routers pay for themselves in a few months

[@hemantchanchlani]

45:43 - statement is incorrect. You cannot connect VPCs with overlapping CIDRs using TGW. It is mentioned in TGW FAQs as well.
Q: Can I connect Amazon VPCs with overlapping CIDRs?
A: AWS Transit Gateway doesn’t support routing between Amazon VPCs with overlapping CIDRs. If you attach a new Amazon VPC that has a CIDR which overlaps with an already attached Amazon VPC, AWS Transit Gateway will not propagate the new Amazon VPC route into the AWS Transit Gateway route table.

[@user-vk8em9nn5d]

Re-read that FAQ carefully. The VPC’s with overlapping CIDR’s cannot be routed to each other. Their routes will not propagate to the same route table. It does not say you cannot attach them both to the TGW. You can attach them to different route tables and add static routes.