#AWS #CloudComputing #Deccansoft #BestDotNetTraining In this video "AWS VPC EC2 Instances in Public and Private Subnets"
, we will be learning and exploring in-depth the various aspects of AWS. Each video is dedicated to a specific concept in AWS. Please subscribe to our channel to stay updated about the latest from us. Don't forget to leave your comment about the videos.
Topics covered:
Amazon Virtual Private Cloud
Amazon VPC lets us provision a logically isolated section of the Amazon Web Services (AWS) cloud where we can launch AWS resources in a virtual network that we define. We can have complete control over our virtual networking environment, including selection of our own IP address ranges, creation of subnets and configuration of route tables and network gateways. We can also create a hardware Virtual Private Network (VPN) connection between our corporate datacenter and our VPC and leverage the AWS cloud as an extension of our corporate datacenter.
Components of Amazon VPC
Amazon VPC comprises a variety of objects that will be familiar to customers with existing networks:
• Virtual Private Cloud: A logically isolated virtual network in the AWS cloud. We define a VPC’s IP address space from ranges we can select.
• Subnet: A segment of a VPC’s IP address range where we can place groups of isolated resources.
• Internet Gateway: The Amazon VPC side of a connection to the public Internet.
• NAT Gateway: A highly available, managed Network Address Translation (NAT) service for our resources in a private subnet to access the Internet.
•
• Amazon VPC Concepts
• As we get started with Amazon VPC, we should understand the key concepts of this virtual network and how it is similar to or different from our own networks. Amazon VPC is the networking layer for Amazon EC2. The key concepts for Amazon VPC are:
•
• VPCs and Subnets
• A virtual private cloud (VPC) is a virtual network dedicated to our AWS account. It is logically isolated from other virtual networks in the AWS Cloud. We can launch your AWS resources, such as Amazon EC2 instances, into our VPC. We can configure our VPC by modifying its IP address range, create subnets, and configure route tables, network gateways and security settings.
VPC and Subnet Sizing
Amazon VPC supports IPv4 and IPv6 addressing and has different CIDR block size limits for each. By default, all VPCs and subnets must have IPv4 CIDR blocks—you can't change this behavior. You can optionally associate an IPv6 CIDR block with your VPC.
VPC and Subnet Sizing for IPv4
When you create a VPC, you must specify an IPv4 CIDR block for the VPC. The allowed block size is between a /16 netmask (65,536 IP addresses) and /28 netmask (16 IP addresses). After you've created your VPC, you can associate secondary CIDR blocks with the VPC.
Subnet Security
AWS provides two features that you can use to increase security in your VPC: security groups and network ACLs. Security groups control inbound and outbound traffic for your instances, and network ACLs control inbound and outbound traffic for your subnets. In most cases, security groups can meet your needs; however, you can also use network ACLs if you want an additional layer of security for our VPC.
Accessing the Internet
You control how the instances that you launch into a VPC access resources outside the VPC.
Your default VPC includes an internet gateway, and each default subnet is a public subnet. Each instance that you launch into a default subnet has a private IPv4 address and a public IPv4 address. These instances can communicate with the internet through the internet gateway. An internet gateway enables our instances to connect to the internet through the Amazon EC2 network edge.
Get Full video tutorial in AWS: Amazon Web Services
------------------------------------------------------------------------------------------------------------------------------------------
For any course related queries reach us @ +91 8008327000, Mrs. Kashmira Shah
Follow links:
For Azure Online Training Please Visit:
0 Comments