Good question .. The DX link is labelled as "private" when it's connected to a VGW because the VGW is for private use only. VGW only allows connectivity to private VPC and therefore only allows private VIF's to connect to it. A DX public VIF cannot connect to a VGW(always private) ; a DX public VIF can only connect to public AWS service(e.g. EC2 with public Elastic IP) or public gateway like S3. Does this answer your query ?
Great presentation! Cant understand why people disliked this video.
As every year, Steve Seymour's DX talk is the best.
Excellent content, all features and details are well-explained. Looking forward to watching re:Invent 2018. Cheers!
Awesome, very helpful presentation!
AWS Networking Masterclass! Thank you...
Great Presentation. Very helful.
Great video ! How can we get the presentation you are using ?
Why does reinvent videos have codes like NET403, 303, or 101. What do they actually mean? Does it tell the depth of the video?
This are level. Every 4xx (400 level) like this are expert level. 1XX are beginner level
at 11:50 why DX link says Private VIF when connected to VGW ? Ideally it should be DX Public VIF no ?
Good question ..
The DX link is labelled as "private" when it's connected to a VGW because the VGW is for private use only. VGW only allows connectivity to private VPC and therefore only allows private VIF's to connect to it. A DX public VIF cannot connect to a VGW(always private) ; a DX public VIF can only connect to public AWS service(e.g. EC2 with public Elastic IP) or public gateway like S3. Does this answer your query ?