AWS re:Invent 2020: Go global with AWS multi-Region network services

A scalable multi-Region network accelerates global expansion and application deployment. Getting there requires a focus on three key areas: (1) global access to applications using a low-latency last-mile network (AWS Global Accelerator vs. DNS vs. Amazon CloudFront), (2) distributed deployment of application stacks using VPC networks spanning AWS Regions and Availability Zones (VPC and AWS Transit Gateway peering and cross-Region AWS PrivateLink), and (3) a scalable and redundant network connecting global VPCs to on-premises data centers (AWS Direct Connect global access). This session dives into these topics, highlighting common challenges and best practices when deploying a scalable multi-Region VPC network infrastructure.
Learn more about re:Invent 2020 at bit.ly/3c4NSdY
Subscribe:
More AWS videos bit.ly/2O3zS75
More AWS events videos bit.ly/316g9t4
#AWS #AWSEvents

[@stukafluka9940]

Hi Sid...in your presentation you mention that the route-tables (both prod and dev) get populated during the traffic-flow (implying that the routes for the destination get added to the route table once the traffic gets to the destination Transit-Gateway). This seems to be a very inefficient and resource-intensive way of routing. I would imagine that the route-tables need to be populated with the routes (both genuine and those that need to be blackholed) before any traffic traversal takes place. Please clarify...and thanks!!!

[@sid2780]

You are correct, route-tables are populated in advance even before any traffic is sent. Apologies if i wasn't clear on that.

[@YinalOZKAN]

Great content presentation!

[@vvmanyam1]

Great overview!!

[@kasukur]

Excellent presentation and great content

[@MrPompyvyas]

Great Content Sid