{ "id": "f2e3ac5b-9d96-4890-8ee9-5667e0192ef5", "created_at": "2026-04-06T00:09:26.365558Z", "updated_at": "2026-04-10T03:20:31.922017Z", "deleted_at": null, "sha1_hash": "e8e304163151af5c8f577149228ba80b55881646", "title": "What is Amazon VPC? - Amazon Virtual Private Cloud", "llm_title": "", "authors": "", "file_creation_date": "0001-01-01T00:00:00Z", "file_modification_date": "0001-01-01T00:00:00Z", "file_size": 65831, "plain_text": "What is Amazon VPC? - Amazon Virtual Private Cloud\r\nArchived: 2026-04-05 18:22:56 UTC\r\nWith Amazon Virtual Private Cloud (Amazon VPC), you can launch AWS resources in a logically isolated virtual\r\nnetwork that you've defined. This virtual network closely resembles a traditional network that you'd operate in\r\nyour own data center, with the benefits of using the scalable infrastructure of AWS.\r\nThe following diagram shows an example VPC. The VPC has one subnet in each of the Availability Zones in the\r\nRegion, EC2 instances in each subnet, and an internet gateway to allow communication between the resources in\r\nyour VPC and the internet.\r\nFor more information, see Amazon Virtual Private Cloud (Amazon VPC).\r\nFeatures\r\nThe following features help you configure a VPC to provide the connectivity that your applications need:\r\nVirtual private clouds (VPC)\r\nA VPC is a virtual network that closely resembles a traditional network that you'd operate in your own data\r\ncenter. After you create a VPC, you can add subnets.\r\nSubnets\r\nA subnet is a range of IP addresses in your VPC. A subnet must reside in a single Availability Zone. After\r\nyou add subnets, you can deploy AWS resources in your VPC.\r\nIP addressing\r\nYou can assign IP addresses, both IPv4 and IPv6, to your VPCs and subnets. You can also bring your\r\npublic IPv4 addresses and IPv6 GUA addresses to AWS and allocate them to resources in your VPC, such\r\nas EC2 instances, NAT gateways, and Network Load Balancers.\r\nRouting\r\nUse route tables to determine where network traffic from your subnet or gateway is directed.\r\nGateways and endpoints\r\nA gateway connects your VPC to another network. For example, use an internet gateway to connect your\r\nVPC to the internet. Use a VPC endpoint to connect to AWS services privately, without the use of an\r\ninternet gateway or NAT device.\r\nPeering connections\r\nhttps://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html\r\nPage 1 of 4\n\nUse a VPC peering connection to route traffic between the resources in two VPCs.\r\nTraffic Mirroring\r\nCopy network traffic from network interfaces and send it to security and monitoring appliances for deep\r\npacket inspection.\r\nTransit gateways\r\nUse a transit gateway, which acts as a central hub, to route traffic between your VPCs, VPN connections,\r\nand Direct Connect connections.\r\nVPC Flow Logs\r\nA flow log captures information about the IP traffic going to and from network interfaces in your VPC.\r\nVPN connections\r\nConnect your VPCs to your on-premises networks using AWS Virtual Private Network (Site-to-Site VPN).\r\nGetting started with Amazon VPC\r\nYour AWS account includes a default VPC in each AWS Region. Your default VPCs are configured such that you\r\ncan immediately start launching and connecting to EC2 instances. For more information, see Plan your VPC.\r\nYou can choose to create additional VPCs with the subnets, IP addresses, gateways and routing that you need. For\r\nmore information, see Create a VPC.\r\nWorking with Amazon VPC\r\nYou can create and manage your VPCs using any of the following interfaces:\r\nAWS Management Console — Provides a web interface that you can use to access your VPCs.\r\nAWS Command Line Interface (AWS CLI) — Provides commands for a broad set of AWS services,\r\nincluding Amazon VPC, and is supported on Windows, Mac, and Linux. For more information, see AWS\r\nCommand Line Interface.\r\nAWS SDKs — Provides language-specific APIs and takes care of many of the connection details, such as\r\ncalculating signatures, handling request retries, and error handling. For more information, see AWS SDKs.\r\nQuery API — Provides low-level API actions that you call using HTTPS requests. Using the Query API is\r\nthe most direct way to access Amazon VPC, but it requires that your application handle low-level details\r\nsuch as generating the hash to sign the request, and error handling. For more information, see Amazon\r\nVPC actions in the Amazon EC2 API Reference.\r\nPricing for Amazon VPC\r\nhttps://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html\r\nPage 2 of 4\n\nThere's no additional charge for using a VPC. There are, however, charges for some VPC components, such as\r\nNAT gateways, IP Address Manager, traffic mirroring, Reachability Analyzer, and Network Access Analyzer. For\r\nmore information, see Amazon VPC Pricing.\r\nNearly all resources that you launch in your virtual private cloud (VPC) provide you with an IP address for\r\nconnectivity. The vast majority of resources in your VPC use private IPv4 addresses. Resources that require direct\r\naccess to the internet over IPv4, however, use public IPv4 addresses.\r\nAmazon VPC enables you to launch managed services, such as Elastic Load Balancing, Amazon RDS, and\r\nAmazon EMR, without having a VPC set up beforehand. It does this by using the default VPC in your account if\r\nyou have one. Any public IPv4 addresses provisioned to your account by the managed service will be charged.\r\nThese charges will be associated with Amazon VPC service in your AWS Cost and Usage Report.\r\nPricing for public IPv4 addresses\r\nA public IPv4 address is an IPv4 address that is routable from the internet. A public IPv4 address is necessary for\r\na resource to be directly reachable from the internet over IPv4.\r\nIf you are an existing or new AWS Free Tier customer, you get 750 hours of public IPv4 address usage with the\r\nEC2 service at no charge. If you are not using the EC2 service in the AWS Free Tier, Public IPv4 addresses are\r\ncharged. For specific pricing information, see the Public IPv4 address tab in Amazon VPC Pricing.\r\nPrivate IPv4 addresses (RFC 1918) are not charged. For more information about how public IPv4 addresses are\r\ncharged for shared VPCs, see Billing and metering for the owner and participants.\r\nPublic IPv4 addresses have the following types:\r\nElastic IP addresses (EIPs): Static, public IPv4 addresses provided by Amazon that you can associate\r\nwith an EC2 instance, elastic network interface, or AWS resource.\r\nEC2 public IPv4 addresses: Public IPv4 addresses assigned to an EC2 instance by Amazon (if the EC2\r\ninstance is launched into a default subnet or if the instance is launched into a subnet that’s been configured\r\nto automatically assign a public IPv4 address).\r\nBYOIPv4 addresses: Public IPv4 addresses in the IPv4 address range that you’ve brought to AWS using\r\nBring your own IP addresses (BYOIP).\r\nService-managed IPv4 addresses: Public IPv4 addresses automatically provisioned on AWS resources\r\nand managed by an AWS service. For example, public IPv4 addresses on Amazon ECS, Amazon RDS, or\r\nAmazon WorkSpaces.\r\nThe following list shows the most common AWS services that can use public IPv4 addresses.\r\nAmazon WorkSpaces Applications\r\nAWS Client VPN\r\nAWS Database Migration Service\r\nhttps://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html\r\nPage 3 of 4\n\nAmazon EC2\r\nAmazon Elastic Container Service\r\nAmazon EKS\r\nAmazon EMR\r\nAmazon GameLift Servers\r\nAWS Global Accelerator\r\nAWS Mainframe Modernization\r\nAmazon Managed Streaming for Apache Kafka\r\nAmazon MQ\r\nAmazon RDS\r\nAmazon Redshift\r\nAWS Site-to-Site VPN\r\nAmazon VPC NAT gateway\r\nAmazon WorkSpaces\r\nElastic Load Balancing\r\nSource: https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html\r\nhttps://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html\r\nPage 4 of 4", "extraction_quality": 1, "language": "EN", "sources": [ "MITRE" ], "references": [ "https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html" ], "report_names": [ "what-is-amazon-vpc.html" ], "threat_actors": [], "ts_created_at": 1775434166, "ts_updated_at": 1775791231, "ts_creation_date": 0, "ts_modification_date": 0, "files": { "pdf": "https://archive.orkl.eu/e8e304163151af5c8f577149228ba80b55881646.pdf", "text": "https://archive.orkl.eu/e8e304163151af5c8f577149228ba80b55881646.txt", "img": "https://archive.orkl.eu/e8e304163151af5c8f577149228ba80b55881646.jpg" } }