AWS re:Invent 2018: Your Virtual Data Center: VPC Fundamentals and Connectivity Options (NET201)
Вставка
- Опубліковано 17 лип 2024
- In this session, we walk through the fundamentals of Amazon VPC. First, we cover build-out and design fundamentals for VPCs, including picking your IP space, subnetting, routing, security, NAT, and much more. We then transition to different approaches and use cases for optionally connecting your VPC to your physical data center with VPN or AWS Direct Connect. This mid-level architecture discussion is aimed at architects, network administrators, and technology decision makers interested in understanding the building blocks that AWS makes available with Amazon VPC. Learn how you can connect VPCs with your offices and current data center footprint.
Upvote if you are here because you have an AWS associate exam. Many thanks for the presentation.
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.
Very nice presentation. Simplifies VPC architecture in understandable terms. A must for mid - beginners.
Brilliant Presentation. Start from the scratch and clear some concepts. !!
Great presentation. I really appreciate being able to see this here on UA-cam.
I fully agree. It's really great that these are published publicly.
She's absolutely wonderful. I could listen to her explain things all day.
indeed, she's a natural.
Thanks for the very clear presentation of VPC and Private networks in general, it's great to learn
Absolutely fantastic! Very nice presentation, well delivered. Thanks!
Very Informative and a quick recap of AWS VPC!!
Excellent! Concise and clear! Thanks!
Gratitude for sharing your Knowledge...
Excellent talk, thank you! This was in preparation for watching the PrivateLink talk next.
Thanks for a detailed explanation. I went through multiple videos to understand VPC, but stopped searching after this video.
Perfect presentation!!!❤🔥
brilliant speech. really good intro to AWS VPCs
Excellent speech, nice and specific to each topic, simple to understand
Thank you, very informative!
Amazing Explanation!
She did a Great Job!
Very nice and clear presentation of VPC and network knowledge.
brilliant session
Great presentation!
Super presentation... very informative
Thanks for excellent explanation.
Excellent Pre!
Very very well explained
Excellent
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?
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?)
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!
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). ^^
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.
25:14 Slide says "VPC CIDR ranges must not overlap"... however, the diagram shows all VPCs with the same CIDR range?
I noticed it too! :) A common (and fun) copy-paste (innocent) error while making presentations / diagrams! :)
😂
True.
cool
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.
NAT gateways can be attached to multiple AZ's
I think it's because they don't bottle-neck like NAT-instances. But hey, you can attach them in multiple AZs.
k