Published Mar 29, 2023
[
 
]
The following features help you configure a VPC to provide the connectivity that your applications need:
A VPC is a virtual network that closely resembles a traditional network that you’d operate in your own data center. After you create a VPC, you can add subnets.
A subnet is a range of IP addresses in your VPC. A subnet must reside in a single Availability Zone. After you add subnets, you can deploy AWS resources in your VPC.
You can assign IPv4 addresses and IPv6 addresses to your VPCs and subnets. You can also bring your public IPv4 and IPv6 GUA addresses to AWS and allocate them to resources in your VPC, such as EC2 instances, NAT gateways, and Network Load Balancers.
Use route tables to determine where network traffic from your subnet or gateway is directed.
A gateway connects your VPC to another network. For example, use an internet gateway to connect your VPC to the internet. Use a VPC endpoint to connect to AWS services privately, without the use of an internet gateway or NAT device.
Use a VPC peering connection to route traffic between the resources in two VPCs.
Copy network traffic from network interfaces and send it to security and monitoring appliances for deep packet inspection.
Use a transit gateway, which acts as a central hub, to route traffic between your VPCs, VPN connections, and AWS Direct Connect connections.
A flow log captures information about the IP traffic going to and from network interfaces in your VPC.
Connect your VPCs to your on-premises networks using AWS Virtual Private Network (AWS VPN).