I try to make the simple, to the point AWS knowledge videos based on my 8+ years of experience working in AWS. Hope you find these videos useful. Kindly subscribe to this channel if you like them and want to be see more.
If you are looking for structured and hands-on lectures, then I recommend to explore my course: www.awswithchetan.com/courses/AWS-VPC-and-Networking
Hi, the edge locations are small and located in cities, there are 600+ edge locations across the world. They host caching devices which are used by CloudFront (CDN) for caching static content like videos, images etc. Also they are connected to AWS region over AWS backbone network. Its an application level service to serve static content. Direct connect connects customer data center to AWS region over a dedicated high speed network. For this there are around 200+ DirectConnect locations across the world where you should terminate the physical links from your datacenter. So both edge locations and direct connect are different.
🎯 Key Takeaways for quick navigation: 00:00 *Understanding AWS networking is crucial for architecture scalability and security across layers 3 to 7 of the OSI model.* 01:21 *Developers should grasp VPC basics, subnetting, and key networking services like load balancers and Route 53 for effective AWS architecture.* 02:14 *DevOps roles require deeper knowledge, including transit gateways, site-to-site VPNs, and network automation using cloud formation or CLI.* 03:35 *AWS networking services are primarily based within VPCs, allowing control over traffic flow and the placement of EC2 instances and components.* 06:13 *Subnets should be created across multiple availability zones for high availability, with public subnets hosting internet-facing components like web servers.* 08:27 *Public subnets have internet access via Internet Gateways, while private subnets rely on NAT Gateways for outbound traffic to the internet.* 13:28 *Hybrid connectivity options include site-to-site VPNs and AWS Direct Connect for secure, reliable connections between on-premises networks and AWS.* 18:52 *VPC peering enables communication between multiple VPCs, while Transit Gateway simplifies complex network architectures by acting as a hub.* 22:27 *VPC Endpoint Services provide secure, efficient access to AWS services like S3 and DynamoDB within the same region, bypassing the internet for data transfer.* 24:12 *Route tables need constant modification for traffic routing via various gateways like transit gateway, VPC peering, VPN connections, Direct Connect, or VPC endpoints.* 24:39 *VPC endpoints come in two types: gateway and interface. Gateway is for accessing S3 or DynamoDB, while interface is for other AWS services like SQS, CloudWatch, SNS, etc., privately from a VPC.* 25:54 *Private Link enables SAS providers to privately expose services from their AWS infrastructure to customer VPCs, ensuring secure and efficient network connectivity without exposing entire VPCs.*
Amazing Video to Learn almost all important services of AWS and System designing for an application in 38 min , I watched it twice to grasp it in my mind and also made notes , thanks a lot Chetan , may god bless you.
but IKEV2 is working, if i disable ikv2 from aws side, then tunnel is showing down from aws side, and from DC side error is "Tunnel1" #1: dropping unexpected IKE_SA_INIT message containing NO_PROPOSAL_CHOSEN notification; message payloads: N; miss" any solution so that i can use ikev1?
Hello! Woud you explain what are the differences between "Click Stream Analysis" and the "Hadoop" while they both analyze clicking data? Much appreciated!
You mentioned that private and public subnets should each have a dedicated route table. The question is: if the dedicated public subnet route table does not have a configured route to the Internet Gateway, but the main route table does, will the public subnet follow the main route table? Similarly, for the private subnet, if the dedicated private route table does not have routes configured to the NAT gateway, but the main route table does, can the private subnet establish a connection to the Internet through NAT?
Hi there, No, subnet can have only one route table associated with it. As soon as you associate a dedicated route table to a subnet it stops following to main route table. Also it’s purely design consideration whether you want to have a dedicated route table per subnet or not. Generally speaking you should have one route table for each type of the subnets. So may be one Public route table which you associate with all Public subnets. Similarly you can create one route table for Private subnets. If there are other subnets which has a different routing requirement (e.g connecting to on-premises network) then you can again create a different route table for such subnets.
@@AWSwithChetan So that means the main route table's routes are only used by subnets that are not associated with any other route table. For a public subnet, if the dedicated(custom) route table associated with it does not have a route to the Internet Gateway, it will not be able to route traffic directly to the internet, even if the main route table has a route to the IGW. This is because the subnet follows the rules of the route table that is explicitly associated with it, and not the main route table and similar for the private subnet. Am I getting it correct?
Thanks for the great video. I have several questions. Could you please help me? - In the senario of DX gateway + private vif, is the bgp session built between DX gateway and customer router to exchange routes? While without DX gateway, the bgp session is built between VGW and customer router? - DX gateways and transit gateways are all virtual software routers and scale according to the volume of traffic? And what about the AWS Direct Connect Router?
