AWS re:Invent 2018: Your Virtual Data Center: VPC Fundamentals and Connectivity Options (NET201)

[@munib1000]

Upvote if you are here because you have an AWS associate exam. Many thanks for the presentation.

[@saltdomeguy]

Very nice presentation. Simplifies VPC architecture in understandable terms. A must for mid - beginners.

[@rodossaenz]

The 50% of a presentation to be understandable is about speaker skills. She did that 100% understandable. Even for people like me that we aren't english native speakers. Congrats and thanks for this presentation.

[@jessesanchez9915]

Great presentation, excellent speaker!

[@Хулиородригес]

Perfect presentation!!!❤🔥

[@michaeldfulton]

Great presentation. I really appreciate being able to see this here on KZbin.

[@bbuggediffy]

I fully agree. It's really great that these are published publicly.

[@frankieliu1211]

Very nice and clear presentation of VPC and network knowledge.

[@lucidjade]

She's absolutely wonderful. I could listen to her explain things all day.

[@joggyjames]

indeed, she's a natural.

[@adkhan123456]

Brilliant Presentation. Start from the scratch and clear some concepts. !!

[@MrKaddu]

Thanks for a detailed explanation. I went through multiple videos to understand VPC, but stopped searching after this video.

[@iamrigank]

Excellent talk, thank you! This was in preparation for watching the PrivateLink talk next.

[@thirien59]

Thanks for the very clear presentation of VPC and Private networks in general, it's great to learn

[@MuhammadKamranAzeem]

Absolutely fantastic! Very nice presentation, well delivered. Thanks!

[@kailashchand7596]

Excellent speech, nice and specific to each topic, simple to understand

[@Vladerrama21]

brilliant session

[@talasilapc]

Very Informative and a quick recap of AWS VPC!!

[@kv-999]

Thanks for excellent explanation.

[@Rickety3263]

Very very well explained

[@daee121]

brilliant speech. really good intro to AWS VPCs

[@inthrakumarp8221]

Super presentation... very informative

[@janardanprajapati2358]

Excellent! Concise and clear! Thanks!

[@kavinrajusridhar2935]

Amazing Explanation!

[@arranduff159]

Great presentation Gina! One question for you. You mentioned that it's possible to block traffic to services other than through a gateway endpoint. Is it possible to do the same for interface endpoints? For example if I want a kinesis stream to only be reachable via my vpc interface endpoint?

[@hkspiritual]

Gratitude for sharing your Knowledge...

[@ARULKS66]

25:14 Slide says "VPC CIDR ranges must not overlap"... however, the diagram shows all VPCs with the same CIDR range?

[@MuhammadKamranAzeem]

I noticed it too! :) A common (and fun) copy-paste (innocent) error while making presentations / diagrams! :)

[@user-wm8xr4bz3b]

😂

[@terrabyte-techy]

True.

[@jeyasekarane]

Great presentation!

[@saxypie]

Thank you, very informative!

[@williammeng2217]

Thanks for your very professional speech. What's the difference between Private Link and Direct Connect? (Private link for the physical network? Direct Connection for overlay network?)

[@brunogustavokilian]

william meng AWS PrivateLink provides private connectivity between VPCs, AWS services, and on-premises applications, securely on the Amazon network (do not leave the aws network) and DirectConnect gives you the ability to establish a dedicated network connection from your premises to AWS. Using AWS Direct Connect, you can establish private connectivity between AWS and your datacenter. Hope it helps you!

[@larskinder1138]

Good presentation. A basic question I have so is, does it make more sense to create VPCs per service, per service cluster (services that could be put in one group) or simply one big VPC containing all services? I have this question, because I did not find anything about that (probably not good in googling). ^^

[@jazzzzzuz]

I think VPC you should consider it similar to local private network, Do you think its a good idea to create multiple network for different service? Again end of the day cloud is all about dynamism and usability these can be changed according to your use-cases.

[@petery3297]

Excellent Pre!

[@AnaximandroAndrade]

Excellent

[@thetecheart]

I don't understand why AWS advertises NAT gateways as an HA resource? NAT gateways reside in a single AZ and are redundant in that AZ only, and in case of an AZ failure, it won't be available. So technically it can't withstand the failure of an AZ. It can be termed as SCALABLE but not at all Highly Available.

[@venkatmms90]

NAT gateways can be attached to multiple AZ's

[@terrabyte-techy]

I think it's because they don't bottle-neck like NAT-instances. But hey, you can attach them in multiple AZs.

[@RakeshKumar-eb9re]

cool

[@gqchen1]

k

[@staj]

She did a Great Job!