# Amazon VPC

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/amazon-vpc

> Amazon VPC (Virtual Private Cloud) is a service that allows users to launch AWS resources in a logically isolated virtual network that they can define and control, including IP address ranges, subnets, route tables, and gateways.

Practice exams covering Amazon VPC: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [AIB-C01 (beta) AWS Certified AI Business Strategist](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist), [AIF-C01 AWS Certified AI Practitioner](https://blowstack.com/practice-exams/aws-certified-ai-practitioner), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional), [MLA-C02 (beta) AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## Free Amazon VPC tools

- [AWS VPC Subnet Calculator](https://blowstack.com/tools/vpc-subnet-calculator): Split a VPC CIDR block into subnets across Availability Zones, with the 5 reserved IPs.
- [AWS VPC Connectivity Troubleshooter](https://blowstack.com/tools/aws-vpc-connectivity-troubleshooter): Find what a resource needs to reach the internet or AWS services, and fix VPC timeouts and errors.
- [AWS IP Address Lookup](https://blowstack.com/tools/aws-ip-address-lookup): Check if an IP address is AWS's and find its Region and service, or list AWS IP ranges.

## 10 key features of Amazon VPC

Amazon VPC offers a secure and isolated network that is customizable, supports multiple connectivity options, includes robust security controls, and is designed for ease of use.

1. **Secure and Isolated Network**: Amazon VPC allows users to provision a logically isolated section of the Amazon Web Services (AWS) cloud where they can launch AWS resources in a virtual network that they define. This provides a secure and isolated environment that can be customized as needed.
2. **Customizable IP Address Range**: Users can select their own IP address range, create subnets, and configure route tables and network gateways. This level of control ensures that networks can be tailored to specific requirements and preferences.
3. **Multiple Connectivity Options**: Amazon VPC offers various connectivity options including connecting to the internet, to userâs existing IT infrastructure via a VPN, or to Amazon Web Services (AWS) resources through private endpoints, offering flexibility in how services and resources are accessed.
4. **Security Controls**: With VPC, users can leverage multiple layers of security, including security groups and network access control lists (ACLs), to help control access to AWS resources within each subnet, thereby enhancing the security posture of their network.
5. **Simple to Use**: Amazon VPC is designed to be easy to configure and manage, even for complex network topologies, through the AWS Management Console, the AWS Command Line Interface (CLI), or SDKs, simplifying the process of setting up and managing a virtual network.
6. **IPv4, IPv6, and Bring Your Own IP**: VPCs and subnets support IPv4 and IPv6 addressing. You can bring public IPv4 and IPv6 GUA addresses to AWS and allocate them to VPC resources such as EC2 instances, NAT gateways, and Network Load Balancers.
7. **Private Service Connectivity**: VPC endpoints connect to AWS services privately without an internet gateway or NAT device.
8. **Traffic Mirroring**: Traffic Mirroring copies traffic from network interfaces to security and monitoring appliances for deep packet inspection.
9. **Transit Gateway Connectivity**: A transit gateway acts as a central routing hub between VPCs, VPN connections, and Direct Connect connections.
10. **VPC Flow Logs**: VPC Flow Logs capture information about IP traffic going to and from network interfaces in a VPC.

## Where Amazon VPC is used

Amazon VPC use cases include hosting secure and scalable web applications, extending on-premise networks to the cloud, enabling disaster recovery strategies, and facilitating development and testing environments.

1. **Host Secure and Scalable Web Applications**: Amazon VPC provides a secure and isolated section of the AWS cloud where you can host web applications. It allows you to control network access to your instances, including selecting your IP address range, creating subnets, and configuring route tables and network gateways. This ensures that your web applications are scalable and isolated from other network traffic, enhancing security and performance.
2. **Extend Your On-Premise Network to the Cloud**: Using Amazon VPC, businesses can extend their on-premise networks into the cloud through a VPN connection. This is beneficial for seamless hybrid cloud deployments, where applications or resources are distributed across on-premise data centers and the AWS cloud, allowing for secure communication between these environments as if they were part of a single, private network.
3. **Disaster Recovery**: By leveraging Amazon VPC, organizations can implement a variety of disaster recovery (DR) strategies. It enables them to quickly replicate their production environment in AWS, facilitating rapid recovery of their IT infrastructure in case of a disaster. This not only minimizes downtime but also ensures that the recovery process is cost-effective and scalable, depending on the criticality of the applications.
4. **Development and Testing Environments**: Amazon VPC allows developers to easily create isolated networks for development and testing purposes. These environments can mimic production environments, ensuring that testing is accurate and effective. The ability to quickly spin up and tear down these environments in a cost-effective manner makes it an ideal choice for continuous integration and continuous deployment (CI/CD) workflows.

## How Amazon VPC is priced

Amazon VPC pricing models include charges for data transfer, VPC Endpoints, NAT Gateways, Elastic IPs, and VPN connections, focusing on resource usage, data volume, and the types of endpoints and connections.

- **Data Transfer Pricing**: Amazon VPC does not charge for creating and using a VPC itself, but charges may apply for VPC-related resources and data transfer. Outbound data transfers from a VPC to the internet, and data transfers between VPCs in different regions, are priced based on the total amount of data transferred, with prices decreasing as data volume increases.
- **VPC Endpoint Pricing**: Using VPC Endpoints allows private connections between your VPC and supported AWS services and VPC endpoint services powered by PrivateLink. Pricing for VPC Endpoints varies depending on the type of endpoint (Interface, Gateway, or Gateway Load Balancer), the region, and the amount of data processed.
- **NAT Gateway Pricing**: NAT Gateways enable instances in a private subnet to connect to the internet or other AWS services, but prevent the internet from initiating a connection with those instances. Pricing for NAT Gateway is based on the hourly rate for the NAT Gateway itself, and the volume of data processed by the gateway.
- **Public IPv4 Address Pricing**: In-use and idle public IPv4 addresses both cost $0.005 per address-hour. Usage is calculated in one-second increments with a minimum of 60 seconds.
- **VPN Connection Pricing**: Amazon VPC offers the option to create an IPsec VPN connection between your VPC and your corporate network. Pricing for VPN connections is based on a per-hour charge for each VPN connection and the data transfer rate.
- **Regional NAT Gateway Pricing**: Regional NAT Gateways incur an hourly charge for each Availability Zone in which they are configured, plus charges per gigabyte processed. Partial gateway-hours are billed as full hours, and hourly billing adjusts when an Availability Zone is removed.
- **IPAM Pricing**: IPAM Free Tier has no IPAM usage charge; other AWS service charges still apply. IPAM Advanced Tier costs $0.00027 per active IP address managed per hour.
- **Traffic Mirroring Pricing**: The ENI owner pays hourly for each network interface enabled for Traffic Mirroring. Charges continue until the associated traffic mirror sessions are deleted, even if the source instance is stopped or terminated.
- **Reachability Analyzer Pricing**: Reachability Analyzer charges per connectivity analysis processed.
- **Network Access Analyzer Pricing**: Network Access Analyzer charges for the number of EC2 elastic network interfaces analyzed in each network assessment.
- **Amazon-Provided Contiguous IPv4 Block Pricing**: Each public IPv4 address in an Amazon-provided contiguous IPv4 block costs $0.008 per hour, with partial hours billed as full hours. All addresses are charged when the block is provisioned, without separate in-use or idle public IPv4 charges.
- **VPC Route Server Pricing**: VPC Route Server is billed per endpoint-hour.
- **VPC Peering Pricing**: VPC peering traffic crossing Availability Zones within the same AWS Region costs $0.01 per GB in both the inbound and outbound directions.
- **ODB Peering Pricing**: ODB peering traffic crossing Availability Zones within the same AWS Region costs $0.01 per GB in both the inbound and outbound directions.
- **VPC Encryption Controls Pricing**: VPC Encryption Controls charges a Region-dependent hourly rate for each non-empty VPC running in monitor or enforce mode. VPC owners are also charged for every VPC attached to a Transit Gateway with encryption support, regardless of whether that VPC has Encryption Controls enabled; attachment to multiple such Transit Gateways does not multiply the hourly VPC charge.

## Services Amazon VPC works with

CloudFront VPC origins allow applications in private subnets to be served through CloudFront without exposing the origins directly to the public internet.

- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Amazon Elastic Compute Cloud (EC2) instances can be launched within a VPC, providing secure and scalable computing capacity.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: Amazon Relational Database Service (RDS) instances can run within a VPC, ensuring your databases are isolated and secure.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Amazon Simple Storage Service (S3) can be accessed privately from within your VPC using VPC endpoints.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: AWS Lambda functions can be configured to run within a VPC, allowing them to access VPC resources securely.
- **[Amazon CloudFront](https://blowstack.com/tools/cloud-services-hub/amazon-cloudfront)**: Amazon CloudFront distributions can be used with VPC origins for secure content delivery from VPC resources.
- **[Elastic Load Balancing (ELB)](https://blowstack.com/tools/cloud-services-hub/elastic-load-balancing-(elb))**: Elastic Load Balancers can distribute traffic to EC2 instances within a VPC, ensuring high availability and scalability.
- **[Amazon API Gateway](https://blowstack.com/tools/cloud-services-hub/amazon-api-gateway)**: Your VPC can access private REST APIs through interface VPC endpoints, and API Gateway VPC links connect APIs to supported private backends inside your VPC.
- **[Amazon AppFlow](https://blowstack.com/tools/cloud-services-hub/amazon-appflow)**: Your VPC can provide private connectivity for supported Amazon AppFlow integrations through AWS PrivateLink, keeping supported SaaS data transfers off the public internet.
- **[Amazon Athena](https://blowstack.com/tools/cloud-services-hub/amazon-athena)**: Your VPC can use an interface endpoint to access Athena APIs privately, without an internet gateway or NAT gateway.
- **[Amazon Augmented AI (Amazon A2I)](https://blowstack.com/tools/cloud-services-hub/amazon-augmented-ai-(amazon-a2i))**: Your VPC can access Amazon A2I runtime APIs through an interface endpoint, allowing applications to start and manage human review loops privately.
- **[Amazon Aurora](https://blowstack.com/tools/cloud-services-hub/amazon-aurora)**: Your VPC hosts Aurora database network interfaces in the subnets selected through a DB subnet group. VPC security groups control which clients can reach the database.
- **[Amazon Aurora Serverless](https://blowstack.com/tools/cloud-services-hub/amazon-aurora-serverless)**: Your VPC supplies the subnets and security groups for Aurora Serverless databases, allowing serverless database capacity to remain privately accessible to application resources.
- **[Amazon Bedrock](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock)**: Your VPC can use interface endpoints to access supported Amazon Bedrock APIs privately, including model inference through the Bedrock Runtime endpoint.
- **[Amazon Bedrock AgentCore](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock-agentcore)**: Your VPC can provide private network access for AgentCore Runtime workloads through configured subnets and security groups, allowing agents to reach private databases and internal services.
- **[Amazon Braket](https://blowstack.com/tools/cloud-services-hub/amazon-braket)**: Your VPC can access Amazon Braket APIs through an interface endpoint, allowing applications to submit and manage quantum tasks without using the public API endpoint.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Your VPC can publish VPC Flow Logs to CloudWatch Logs and expose networking metrics, such as NAT gateway metrics, in CloudWatch. CloudWatch alarms can notify you about conditions such as dropped packets or port allocation failures.
- **[Amazon CodeGuru](https://blowstack.com/tools/cloud-services-hub/amazon-codeguru)**: Your VPC can use interface endpoints for supported CodeGuru Reviewer and CodeGuru Profiler APIs, keeping code-review requests and profiling communications on private connections.
- **[Amazon CodeWhisperer](https://blowstack.com/tools/cloud-services-hub/amazon-codewhisperer)**: Your VPC can use a CodeWhisperer interface endpoint to provide private connectivity for supported coding-assistant requests.
- **[Amazon Comprehend](https://blowstack.com/tools/cloud-services-hub/amazon-comprehend)**: Your VPC can access Comprehend APIs through an interface endpoint. Supported Comprehend analysis jobs can also use VPC configurations to access resources through selected subnets and security groups.
- **[Amazon Connect](https://blowstack.com/tools/cloud-services-hub/amazon-connect)**: Your VPC can access supported Amazon Connect APIs through interface endpoints, providing private connectivity for applications that manage contact-center resources.
- **[Amazon Data Firehose](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-firehose)**: Your VPC can deliver VPC Flow Logs directly to Amazon Data Firehose for processing and delivery. Firehose can also create network interfaces in selected VPC subnets to reach supported private destinations.
- **[Amazon DataZone](https://blowstack.com/tools/cloud-services-hub/amazon-datazone)**: Your VPC can access Amazon DataZone APIs through an interface endpoint, allowing private management of data catalogs, projects, and subscriptions.
- **[Amazon Detective](https://blowstack.com/tools/cloud-services-hub/amazon-detective)**: Your VPC can access Amazon Detective APIs through an interface endpoint, allowing investigation tools to communicate with Detective privately.
- **[Amazon DevOps Guru](https://blowstack.com/tools/cloud-services-hub/amazon-devops-guru)**: Your VPC can access DevOps Guru APIs through an interface endpoint, allowing private retrieval and management of operational insights.
- **[Amazon DocumentDB (with MongoDB compatibility)](https://blowstack.com/tools/cloud-services-hub/amazon-documentdb-(with-mongodb-compatibility))**: Your VPC hosts DocumentDB clusters using a DB subnet group, with security groups controlling database access. Applications can connect through private cluster and instance endpoints.
- **[Amazon DynamoDB](https://blowstack.com/tools/cloud-services-hub/amazon-dynamodb)**: Your VPC can use a DynamoDB gateway endpoint to route database requests privately without an internet gateway or NAT gateway. Endpoint policies can restrict which DynamoDB resources are accessible.
- **[Amazon EC2 Auto Scaling](https://blowstack.com/tools/cloud-services-hub/amazon-ec2-auto-scaling)**: Your VPC supplies the subnets where EC2 Auto Scaling launches instances. An Auto Scaling group can distribute capacity across subnets in multiple Availability Zones.
- **[Amazon Elastic Block Store (Amazon EBS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-block-store-(amazon-ebs))**: Your VPC can access EBS direct APIs through an interface endpoint, allowing private applications to read or write snapshot blocks without using public endpoints.
- **[Amazon Elastic Container Registry (Amazon ECR)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-registry-(amazon-ecr))**: Your VPC can use ECR API and Docker registry interface endpoints for private registry access. Private image pulls also require access to the S3 storage used for image layers, commonly through an S3 gateway endpoint.
- **[Amazon Elastic Container Service (Amazon ECS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-service-(amazon-ecs))**: Your VPC provides networking for ECS container instances and tasks. Tasks using awsvpc networking receive network interfaces in selected subnets and can have their own security groups.
- **[Amazon Elastic File System (Amazon EFS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-file-system-(amazon-efs))**: Your VPC hosts EFS mount targets in selected subnets, providing private NFS access to file systems. Security groups on the mount targets control which clients can mount them.
- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: Your VPC supplies networking for EKS clusters, nodes, and pods. EKS supports private Kubernetes API endpoint access, while the Amazon VPC CNI assigns VPC addresses to pods.
- **[Amazon ElastiCache](https://blowstack.com/tools/cloud-services-hub/amazon-elasticache)**: Your VPC hosts ElastiCache resources in selected subnets, with security groups controlling client access. Cache endpoints let applications communicate with the cache over private networking.
- **[Amazon EMR](https://blowstack.com/tools/cloud-services-hub/amazon-emr)**: Your VPC hosts EMR clusters in selected subnets and controls cluster connectivity through routing and security groups. EMR Serverless applications can also use VPC connectivity to reach private data sources.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: Your VPC can access EventBridge APIs through interface endpoints. EventBridge Pipes can also use configured VPC subnets and security groups to connect to supported private sources, such as Kafka clusters.
- **[Amazon Forecast](https://blowstack.com/tools/cloud-services-hub/amazon-forecast)**: Your VPC can access Forecast and Forecast Query APIs through interface endpoints, keeping forecasting management and query requests private.
- **[Amazon Fraud Detector](https://blowstack.com/tools/cloud-services-hub/amazon-fraud-detector)**: Your VPC can access Amazon Fraud Detector through an interface endpoint, allowing applications to request fraud predictions without traversing the public internet.
- **[Amazon FSx](https://blowstack.com/tools/cloud-services-hub/amazon-fsx-(for-all-types))**: Your VPC supplies subnets and security groups for FSx file systems and their network interfaces. Clients access the file systems through private network endpoints using the protocols supported by the selected FSx service.
- **[Amazon GameLift](https://blowstack.com/tools/cloud-services-hub/amazon-gamelift)**: Your VPC can peer with the VPC used by supported GameLift managed fleets, allowing game servers to reach private resources such as databases and backend services.
- **[Amazon GuardDuty](https://blowstack.com/tools/cloud-services-hub/amazon-guardduty)**: Your VPC network activity is analyzed by GuardDuty using VPC flow-log data obtained directly from AWS infrastructure. GuardDuty can detect suspicious traffic without requiring you to create or deliver your own flow logs.
- **[Amazon HealthLake](https://blowstack.com/tools/cloud-services-hub/amazon-healthlake)**: Your VPC can access HealthLake through interface endpoints, providing private connectivity for supported healthcare data APIs.
- **[Amazon Inspector](https://blowstack.com/tools/cloud-services-hub/amazon-inspector)**: Your VPC networking configuration is examined by Inspector when it assesses EC2 network reachability. Findings identify reachable network paths using components such as security groups, network ACLs, and routing.
- **[Amazon Kendra](https://blowstack.com/tools/cloud-services-hub/amazon-kendra)**: Your VPC can provide private access for supported Kendra data source connectors through configured subnets and security groups. This allows Kendra to index repositories that are not publicly reachable.
- **[Amazon Keyspaces (for Apache Cassandra)](https://blowstack.com/tools/cloud-services-hub/amazon-keyspaces-(for-apache-cassandra))**: Your VPC can use an interface endpoint to connect privately to Amazon Keyspaces with Cassandra clients. Endpoint policies and security groups provide additional access controls.
- **[Amazon Kinesis Data Streams](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-streams)**: Your VPC can use a Kinesis Data Streams interface endpoint for private producer and consumer traffic, without requiring a NAT gateway or internet gateway.
- **[Amazon Kinesis Video Streams](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-video-streams)**: Your VPC can use interface endpoints for supported Kinesis Video Streams APIs, providing private connectivity for video-streaming applications.
- **[Amazon Lex](https://blowstack.com/tools/cloud-services-hub/amazon-lex)**: Your VPC can use interface endpoints for supported Lex management and runtime APIs, allowing applications to manage bots and conduct conversations privately.
- **[Amazon Lightsail](https://blowstack.com/tools/cloud-services-hub/amazon-lightsail)**: Your default VPC can be peered with a Lightsail VPC in the same Region, allowing Lightsail instances to reach private resources in that VPC.
- **[Amazon Location Service](https://blowstack.com/tools/cloud-services-hub/amazon-location-service)**: Your VPC can access supported Amazon Location Service APIs through interface endpoints, keeping location-service requests on private network paths.
- **[Amazon Macie](https://blowstack.com/tools/cloud-services-hub/amazon-macie)**: Your VPC can access Macie APIs through an interface endpoint, allowing private management of sensitive-data discovery jobs and findings.
- **[Amazon Managed Blockchain](https://blowstack.com/tools/cloud-services-hub/amazon-managed-blockchain)**: Your VPC can use the interface endpoint associated with a Managed Blockchain Hyperledger Fabric network to access its blockchain resources privately.
- **[Amazon Managed Service for Apache Flink](https://blowstack.com/tools/cloud-services-hub/amazon-managed-service-for-apache-flink)**: Your VPC can provide network connectivity for Flink applications through selected subnets and security groups. The service creates network interfaces so applications can read from or write to private resources.
- **[Amazon Managed Service for Prometheus](https://blowstack.com/tools/cloud-services-hub/amazon-managed-service-for-prometheus)**: Your VPC can use interface endpoints for Amazon Managed Service for Prometheus control-plane and workspace APIs, allowing private metric ingestion and queries.
- **[Amazon Managed Streaming for Apache Kafka](https://blowstack.com/tools/cloud-services-hub/amazon-managed-streaming-for-apache-kafka)**: Your VPC supplies subnets and security groups for MSK brokers and client connectivity. MSK also supports managed multi-VPC private connectivity for clients in other VPCs.
- **[Amazon Managed Workflows for Apache Airflow (Amazon MWAA)](https://blowstack.com/tools/cloud-services-hub/amazon-managed-workflows-for-apache-airflow-(amazon-mwaa))**: Your VPC supplies the private subnets and security groups used by an MWAA environment. You can also configure private webserver access and let workflows reach private resources.
- **[Amazon MemoryDB for Redis](https://blowstack.com/tools/cloud-services-hub/amazon-memorydb-for-redis)**: Your VPC hosts MemoryDB clusters using a subnet group, with security groups controlling access to the cluster endpoints.
- **[Amazon MQ](https://blowstack.com/tools/cloud-services-hub/amazon-mq)**: Your VPC hosts Amazon MQ broker network interfaces in selected subnets. Private broker endpoints and security groups restrict messaging access to connected networks.
- **[Amazon Neptune](https://blowstack.com/tools/cloud-services-hub/amazon-neptune)**: Your VPC hosts Neptune databases in subnets selected through a DB subnet group. Security groups control connections to the database's private endpoints.
- **[Amazon OpenSearch Service](https://blowstack.com/tools/cloud-services-hub/amazon-opensearch-service)**: Your VPC can host an OpenSearch Service domain's network interfaces, keeping its endpoint privately reachable. Subnet selection and security groups control connectivity to the domain.
- **[Amazon Personalize](https://blowstack.com/tools/cloud-services-hub/amazon-personalize)**: Your VPC can access supported Personalize management, events, and runtime APIs through interface endpoints, allowing private recommendation requests and event ingestion.
- **[Amazon Polly](https://blowstack.com/tools/cloud-services-hub/amazon-polly)**: Your VPC can use a Polly interface endpoint to submit text-to-speech requests privately.
- **[Amazon Q](https://blowstack.com/tools/cloud-services-hub/amazon-q)**: Your VPC can use supported Amazon Q Developer interface endpoints to provide private connectivity for developer-assistance features.
- **[Amazon Q Business](https://blowstack.com/tools/cloud-services-hub/amazon-q-business)**: Your VPC can provide private connectivity for supported Amazon Q Business APIs. Supported data source connectors can also use configured VPC subnets and security groups to reach private repositories.
- **[Amazon QuickSight](https://blowstack.com/tools/cloud-services-hub/amazon-quicksight)**: Your VPC can be connected to QuickSight through a VPC connection, which creates network interfaces in selected subnets. This lets QuickSight query private databases without exposing them publicly.
- **[Amazon RDS Proxy](https://blowstack.com/tools/cloud-services-hub/amazon-rds-proxy)**: Your VPC hosts RDS Proxy endpoints in selected subnets, with security groups governing client and database connections. Additional proxy endpoints can provide access from other VPCs.
- **[Amazon Redshift](https://blowstack.com/tools/cloud-services-hub/amazon-redshift)**: Your VPC supplies subnets and security groups for Redshift clusters and Serverless workgroups. Enhanced VPC routing can route supported data-loading and unloading traffic through your VPC.
- **[Amazon Rekognition](https://blowstack.com/tools/cloud-services-hub/amazon-rekognition)**: Your VPC can access Rekognition APIs through an interface endpoint, allowing image and video analysis requests to remain private.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: Your VPC can associate with Route 53 private hosted zones for private DNS resolution. Route 53 Resolver endpoints support hybrid DNS, and Resolver DNS Firewall filters DNS queries from VPC resources.
- **[Amazon SageMaker](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker)**: Your VPC can provide network interfaces for supported SageMaker training, processing, and inference workloads through VPC configurations. Interface endpoints also provide private access to SageMaker APIs and hosted inference.
- **[Amazon SageMaker Data Wrangler](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker-data-wrangler)**: Your VPC can contain the SageMaker environment used by Data Wrangler, allowing data preparation to access private data sources. VPC-only configurations require network paths to the AWS services used by the workflow.
- **[Amazon SageMaker Ground Truth](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker-ground-truth)**: Your VPC can provide private access to a Ground Truth private workforce's labeling portal through a workforce VPC configuration.
- **[Amazon Security Lake](https://blowstack.com/tools/cloud-services-hub/amazon-security-lake)**: Your VPC flow-log events can be collected by Security Lake as a native AWS source. Security Lake normalizes these events into its common security schema and stores them for analysis.
- **[Amazon Simple Email Service (Amazon SES)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-email-service-(amazon-ses))**: Your VPC can use an SES SMTP interface endpoint to send email privately from applications, without requiring internet access to the SMTP endpoint.
- **[Amazon Simple Notification Service (Amazon SNS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-notification-service-(amazon-sns))**: Your VPC can publish messages to SNS through an interface endpoint. An endpoint policy can restrict which topics and actions are available through that connection.
- **[Amazon Simple Queue Service (Amazon SQS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-queue-service-(amazon-sqs))**: Your VPC can access SQS through an interface endpoint, allowing applications to send, receive, and delete messages privately.
- **[Amazon Textract](https://blowstack.com/tools/cloud-services-hub/amazon-textract)**: Your VPC can access Textract APIs through an interface endpoint, allowing applications to submit document-analysis requests privately.
- **[Amazon Timestream](https://blowstack.com/tools/cloud-services-hub/amazon-timestream)**: Your VPC can use interface endpoints for Timestream for LiveAnalytics ingestion and query APIs, keeping time-series writes and queries off the public internet.
- **[Amazon Timestream for InfluxDB](https://blowstack.com/tools/cloud-services-hub/amazon-timestream-for-influxdb)**: Your VPC hosts Timestream for InfluxDB database network interfaces in selected subnets. Security groups control access to the InfluxDB endpoint.
- **[Amazon Transcribe](https://blowstack.com/tools/cloud-services-hub/amazon-transcribe)**: Your VPC can use supported Transcribe interface endpoints for private transcription API access, including supported streaming connections.
- **[Amazon Translate](https://blowstack.com/tools/cloud-services-hub/amazon-translate)**: Your VPC can access Translate through an interface endpoint, allowing applications to submit translation requests privately.
- **[Amazon Verified Permissions](https://blowstack.com/tools/cloud-services-hub/amazon-verified-permissions)**: Your VPC can access Verified Permissions through an interface endpoint, allowing applications to request authorization decisions privately.
- **[Amazon WorkSpaces](https://blowstack.com/tools/cloud-services-hub/amazon-workspaces)**: Your VPC supplies subnets and security groups for WorkSpaces desktops, allowing them to access private applications and connected corporate networks.
- **[Amazon WorkSpaces Applications](https://blowstack.com/tools/cloud-services-hub/amazon-appstream-2)**: Your VPC provides network connectivity for WorkSpaces Applications streaming instances through selected subnets and security groups. Streamed applications can reach private databases, file shares, and internal services.
- **[Amazon WorkSpaces Secure Browser](https://blowstack.com/tools/cloud-services-hub/amazon-workspaces-web)**: Your VPC supplies subnets and security groups for WorkSpaces Secure Browser sessions, allowing browser users to access private websites and applications through your network.
- **[AWS App Runner](https://blowstack.com/tools/cloud-services-hub/aws-app-runner)**: Your VPC can receive outbound application traffic from App Runner through a VPC connector. App Runner also supports private incoming access through VPC ingress connections and interface endpoints.
- **[AWS AppConfig](https://blowstack.com/tools/cloud-services-hub/aws-appconfig)**: Your VPC can use interface endpoints for AppConfig management and configuration-data APIs, allowing applications and agents to retrieve configuration privately.
- **[AWS Application Discovery Service](https://blowstack.com/tools/cloud-services-hub/aws-application-discovery-service)**: Your VPC can use Application Discovery Service interface endpoints for supported discovery APIs and agent communications.
- **[AWS Application Migration Service](https://blowstack.com/tools/cloud-services-hub/aws-application-migration-service)**: Your VPC supplies the staging subnet for Application Migration Service replication servers and the networking used by launched test or cutover instances. Private connectivity can be configured for supported service communications.
- **[AWS Artifact](https://blowstack.com/tools/cloud-services-hub/aws-artifact)**: Your VPC can access AWS Artifact through an interface endpoint, providing private API access for supported compliance-report operations.
- **[AWS Audit Manager](https://blowstack.com/tools/cloud-services-hub/aws-audit-manager)**: Your VPC can access Audit Manager APIs through an interface endpoint, keeping assessment and evidence-management requests private.
- **[AWS Auto Scaling](https://blowstack.com/tools/cloud-services-hub/aws-auto-scaling)**: Your VPC can access AWS Auto Scaling scaling-plan APIs through an interface endpoint, allowing private management of scaling plans.
- **[AWS Backup](https://blowstack.com/tools/cloud-services-hub/aws-backup)**: Your VPC can access AWS Backup APIs through an interface endpoint, allowing backup-management applications to operate without using public service endpoints.
- **[AWS Batch](https://blowstack.com/tools/cloud-services-hub/aws-batch)**: Your VPC supplies subnets and security groups for Batch compute environments. Jobs run on EC2 or Fargate resources connected to those subnets and can access private resources.
- **[AWS Billing and Cost Management](https://blowstack.com/tools/cloud-services-hub/aws-billing-and-cost-management)**: Your VPC can use supported Billing and Cost Management interface endpoints to access billing APIs privately.
- **[AWS Billing Conductor](https://blowstack.com/tools/cloud-services-hub/aws-billing-conductor)**: Your VPC can access Billing Conductor APIs through an interface endpoint, allowing private management of billing groups and custom pricing.
- **[AWS Certificate Manager (ACM)](https://blowstack.com/tools/cloud-services-hub/aws-certificate-manager-(acm))**: Your VPC can access ACM APIs through an interface endpoint, allowing private certificate-management requests.
- **[AWS Clean Rooms](https://blowstack.com/tools/cloud-services-hub/aws-clean-rooms)**: Your VPC can access supported AWS Clean Rooms APIs through interface endpoints, allowing applications to manage collaborations and analysis requests privately.
- **[AWS Client VPN](https://blowstack.com/tools/cloud-services-hub/aws-client-vpn)**: Your VPC can associate subnets with a Client VPN endpoint to give authenticated users remote access to private resources. Client VPN routes and authorization rules determine which networks users can reach.
- **[AWS Cloud Map](https://blowstack.com/tools/cloud-services-hub/aws-cloud-map)**: Your VPC can be associated with a Cloud Map private DNS namespace. Cloud Map registers service instances in a private hosted zone so VPC clients can discover them through DNS.
- **[AWS Cloud9](https://blowstack.com/tools/cloud-services-hub/aws-cloud9)**: Your VPC can host a Cloud9 EC2 development environment in a selected subnet. Routing and security groups control the environment's access to private resources and external services.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: Your VPC and its networking components can be provisioned as CloudFormation resources, including subnets, route tables, gateways, security groups, and endpoints. Stacks can manage these resources together as a repeatable network deployment.
- **[AWS CloudHSM](https://blowstack.com/tools/cloud-services-hub/aws-cloudhsm)**: Your VPC hosts CloudHSM network interfaces in selected subnets. Clients connect privately to HSMs, with security groups controlling access.
- **[AWS CloudShell](https://blowstack.com/tools/cloud-services-hub/aws-cloudshell)**: Your VPC can host a CloudShell VPC environment using selected subnets and security groups. The shell can then access private resources through your VPC's networking.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: Your VPC management API activity, such as changes to routes and security groups, is recorded by CloudTrail. A CloudTrail interface endpoint also supports private access to CloudTrail APIs.
- **[AWS CodeArtifact](https://blowstack.com/tools/cloud-services-hub/aws-codeartifact)**: Your VPC can use CodeArtifact API and repository interface endpoints to access private package repositories. Package downloads also require access to the S3 storage used by CodeArtifact.
- **[AWS CodeBuild](https://blowstack.com/tools/cloud-services-hub/aws-codebuild)**: Your VPC can host network interfaces for CodeBuild builds using selected subnets and security groups. Builds can then access private dependencies, databases, and internal test services.
- **[AWS CodeCommit](https://blowstack.com/tools/cloud-services-hub/aws-codecommit)**: Your VPC can use CodeCommit API and Git interface endpoints to manage repositories and perform supported Git operations privately.
- **[AWS CodeConnections](https://blowstack.com/tools/cloud-services-hub/aws-codeconnections)**: Your VPC can provide connectivity for CodeConnections hosts that represent supported self-managed source providers. Configured subnets and security groups let the connection reach installations such as a private GitHub Enterprise Server.
- **[AWS CodeDeploy](https://blowstack.com/tools/cloud-services-hub/aws-codedeploy)**: Your VPC can use CodeDeploy interface endpoints for supported deployment API and agent communications, allowing deployments to private instances without public service access.
- **[AWS CodePipeline](https://blowstack.com/tools/cloud-services-hub/aws-codepipeline)**: Your VPC can access CodePipeline APIs through an interface endpoint, allowing private management and invocation of release pipelines.
- **[AWS Compute Optimizer](https://blowstack.com/tools/cloud-services-hub/aws-compute-optimizer)**: Your VPC can access Compute Optimizer APIs through an interface endpoint, allowing applications to retrieve optimization recommendations privately.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: Your VPC resources and configuration changes can be recorded by AWS Config. Managed and custom rules can evaluate conditions such as unrestricted security groups, public subnet routing, or required flow logging.
- **[AWS Control Tower](https://blowstack.com/tools/cloud-services-hub/aws-control-tower)**: Your VPC configuration can be governed through Control Tower controls, and Account Factory can create standardized VPC networking for newly provisioned accounts.
- **[AWS Cost and Usage Report](https://blowstack.com/tools/cloud-services-hub/aws-cost-and-usage-report)**: Your VPC can access supported Cost and Usage Report management APIs through an interface endpoint, allowing private management of report definitions.
- **[AWS Cost Explorer](https://blowstack.com/tools/cloud-services-hub/aws-cost-explorer)**: Your VPC can access Cost Explorer APIs through an interface endpoint, allowing private cost and usage queries.
- **[AWS Data Exchange](https://blowstack.com/tools/cloud-services-hub/aws-data-exchange)**: Your VPC can access AWS Data Exchange APIs through an interface endpoint, allowing private management of supported data-product and data-set operations.
- **[AWS Data Pipeline](https://blowstack.com/tools/cloud-services-hub/aws-data-pipeline)**: Your VPC can host EC2 resources launched by Data Pipeline in a specified subnet. Pipeline task runners can then process data using private network access.
- **[AWS Database Migration Service (AWS DMS)](https://blowstack.com/tools/cloud-services-hub/aws-database-migration-service-(aws-dms))**: Your VPC supplies subnets and security groups for DMS replication resources. Those resources use your network routes to connect to source and target databases.
- **[AWS DataSync](https://blowstack.com/tools/cloud-services-hub/aws-datasync)**: Your VPC can provide private connectivity for DataSync agents through VPC endpoints. DataSync also creates network interfaces in selected subnets when accessing supported VPC-hosted storage.
- **[AWS Device Farm](https://blowstack.com/tools/cloud-services-hub/aws-device-farm)**: Your VPC can be connected to supported Device Farm private-device tests through VPC-ENI connectivity. Tests can then reach private application backends using selected subnets and security groups.
- **[AWS Direct Connect](https://blowstack.com/tools/cloud-services-hub/aws-direct-connect)**: Your VPC can connect to an on-premises network through Direct Connect using a private virtual interface and a virtual private gateway, or through a transit gateway architecture.
- **[AWS Directory Service](https://blowstack.com/tools/cloud-services-hub/aws-directory-service)**: Your VPC hosts network interfaces for supported Directory Service directories in selected subnets. Directory DNS addresses and security groups support private domain membership, authentication, and directory access.
- **[AWS Elastic Beanstalk](https://blowstack.com/tools/cloud-services-hub/aws-elastic-beanstalk)**: Your VPC can host Elastic Beanstalk environments using configured instance and load balancer subnets. You can place application instances in private subnets while exposing only the load balancer.
- **[AWS Elastic Disaster Recovery](https://blowstack.com/tools/cloud-services-hub/aws-elastic-disaster-recovery)**: Your VPC supplies the staging subnet used for Elastic Disaster Recovery replication and the network settings for recovered instances. Recovery configurations can place instances in isolated test or production subnets.
- **[AWS Entity Resolution](https://blowstack.com/tools/cloud-services-hub/aws-entity-resolution)**: Your VPC can access Entity Resolution APIs through an interface endpoint, allowing private management of matching workflows and related resources.
- **[AWS Fargate](https://blowstack.com/tools/cloud-services-hub/aws-fargate)**: Your VPC supplies networking for Fargate tasks and pods. Each workload receives a network interface in a selected subnet, with security groups controlling traffic.
- **[AWS Fault Injection Service](https://blowstack.com/tools/cloud-services-hub/aws-fault-injection-simulator-(aws-fis))**: Your VPC subnets can be targeted by supported Fault Injection Service network-disruption actions. Experiments can test how applications behave when connectivity is interrupted.
- **[AWS Firewall Manager](https://blowstack.com/tools/cloud-services-hub/aws-firewall-manager)**: Your VPC security can be governed centrally with Firewall Manager policies for security groups, Network Firewall, and Route 53 Resolver DNS Firewall. Policies can apply protections across accounts and remediate supported configuration violations.
- **[AWS Global Accelerator](https://blowstack.com/tools/cloud-services-hub/aws-global-accelerator)**: Your VPC can contain private application endpoints reached through Global Accelerator, such as internal Application Load Balancers and private EC2 instances. Global Accelerator provides public entry points without requiring those backends to have public IP addresses.
- **[AWS Glue](https://blowstack.com/tools/cloud-services-hub/aws-glue)**: Your VPC can provide private connectivity for Glue jobs through connections that specify subnets and security groups. Glue creates network interfaces so jobs can reach private databases and other resources.
- **[AWS Glue DataBrew](https://blowstack.com/tools/cloud-services-hub/aws-glue-databrew)**: Your VPC can provide connectivity for DataBrew projects and jobs that use supported private data sources. Configured subnets and security groups govern access through Glue connections.
- **[AWS Health Dashboard](https://blowstack.com/tools/cloud-services-hub/aws-health-dashboard)**: Your VPC can access AWS Health APIs through an interface endpoint, allowing private retrieval of supported service-health and account-event information.
- **[AWS IAM Identity Center (AWS Single Sign-On)](https://blowstack.com/tools/cloud-services-hub/aws-iam-identity-center-(aws-single-sign-on))**: Your VPC can use supported IAM Identity Center interface endpoints for private access to identity, authentication, and account-access APIs.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: Your VPC resources can be managed under IAM policies that control networking actions such as creating subnets or changing security groups. VPC endpoint policies and supported VPC-related condition keys can further restrict access to AWS services.
- **[AWS IoT Core](https://blowstack.com/tools/cloud-services-hub/aws-iot-core)**: Your VPC can use supported IoT Core interface endpoints for private device-data and credentials-provider communications. Devices can reach these endpoints through connected private networks.
- **[AWS IoT Device Management](https://blowstack.com/tools/cloud-services-hub/aws-iot-device-management)**: Your VPC can use an IoT Jobs data-plane interface endpoint for supported device job communications, allowing connected devices to exchange job information privately.
- **[AWS IoT Greengrass](https://blowstack.com/tools/cloud-services-hub/aws-iot-greengrass)**: Your VPC can provide interface endpoints for supported Greengrass service communications. Core devices on connected private networks can use these endpoints alongside the other AWS endpoints required by their components.
- **[AWS IoT SiteWise](https://blowstack.com/tools/cloud-services-hub/aws-iot-sitewise)**: Your VPC can access supported IoT SiteWise APIs through interface endpoints, providing private connectivity for industrial asset management and data operations.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: Your VPC can access KMS through an interface endpoint, allowing private encryption, decryption, and key-management requests. Endpoint policies can restrict permitted keys and operations.
- **[AWS Lake Formation](https://blowstack.com/tools/cloud-services-hub/aws-lake-formation)**: Your VPC can access Lake Formation APIs through an interface endpoint, allowing private data-lake permission and governance requests.
- **[AWS Launch Wizard](https://blowstack.com/tools/cloud-services-hub/aws-launch-wizard)**: Your VPC can be selected or created during supported Launch Wizard deployments. Launch Wizard configures application resources across appropriate subnets and creates required networking and security-group settings.
- **[AWS License Manager](https://blowstack.com/tools/cloud-services-hub/aws-license-manager)**: Your VPC can access supported License Manager APIs through interface endpoints, allowing private license-management operations.
- **[AWS Local Zones](https://blowstack.com/tools/cloud-services-hub/aws-local-zones)**: Your VPC can extend into a Local Zone through a subnet created in that zone. Resources in the subnet use VPC routing and security controls while running closer to local users.
- **[AWS Managed Services (AMS)](https://blowstack.com/tools/cloud-services-hub/aws-managed-services-(ams))**: Your VPC networking can be provisioned and operated through supported AMS management processes, including changes to subnets, routes, security groups, and connectivity.
- **[AWS Marketplace](https://blowstack.com/tools/cloud-services-hub/aws-marketplace)**: Your VPC can host software purchased through AWS Marketplace, including virtual network appliances deployed on EC2. Marketplace firewall and monitoring appliances can also be used with VPC routing, Gateway Load Balancer endpoints, or Traffic Mirroring where supported.
- **[AWS Migration Hub](https://blowstack.com/tools/cloud-services-hub/aws-migration-hub)**: Your VPC can access supported Migration Hub APIs through interface endpoints, allowing private migration-tracking and coordination requests.
- **[AWS Network Firewall](https://blowstack.com/tools/cloud-services-hub/aws-network-firewall)**: Your VPC can deploy Network Firewall endpoints in dedicated subnets and route traffic through them for inspection. Firewall policies can filter inbound, outbound, and inter-subnet traffic.
- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: Your VPC can access Organizations APIs through a supported interface endpoint, allowing private organization-management requests.
- **[AWS Outposts](https://blowstack.com/tools/cloud-services-hub/aws-outposts)**: Your VPC can extend to an Outpost through Outpost subnets. Resources in those subnets use VPC addressing and security controls, with local gateway routing available for supported on-premises connectivity.
- **[AWS Private Certificate Authority](https://blowstack.com/tools/cloud-services-hub/aws-private-certificate-authority)**: Your VPC can access Private CA APIs through an interface endpoint, allowing private certificate issuance and certificate-authority management.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: Your VPC can use PrivateLink endpoints to access supported AWS services and privately published endpoint services. Endpoint network interfaces provide private entry points controlled by security groups and supported endpoint policies.
- **[AWS Resilience Hub](https://blowstack.com/tools/cloud-services-hub/aws-resilience-hub)**: Your VPC can access Resilience Hub APIs through an interface endpoint, allowing private management of resilience assessments and recommendations.
- **[AWS Resource Access Manager (AWS RAM)](https://blowstack.com/tools/cloud-services-hub/aws-resource-access-manager-(aws-ram))**: Your VPC subnets can be shared through RAM with other accounts in your organization. Participants can deploy supported resources while the VPC owner retains control of the shared network.
- **[AWS Resource Groups and Tag Editor](https://blowstack.com/tools/cloud-services-hub/aws-resource-groups-and-tag-editor)**: Your VPC can access supported Resource Groups and tagging APIs through interface endpoints, allowing private resource-group and tag-management operations.
- **[AWS Secrets Manager](https://blowstack.com/tools/cloud-services-hub/aws-secrets-manager)**: Your VPC can use a Secrets Manager interface endpoint for private secret retrieval and management. This also supports rotation functions in private subnets that need to access Secrets Manager.
- **[AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub)**: Your VPC security configuration can be evaluated through Security Hub controls, including checks for unrestricted security groups and missing flow logs. Findings identify network configurations that violate enabled security standards.
- **[AWS Security Token Service (AWS STS)](https://blowstack.com/tools/cloud-services-hub/aws-security-token-service-(aws-sts))**: Your VPC can use a regional STS interface endpoint to request temporary AWS credentials privately.
- **[AWS Serverless Application Repository](https://blowstack.com/tools/cloud-services-hub/aws-serverless-application-repository)**: Your VPC can access Serverless Application Repository APIs through an interface endpoint, allowing private discovery and management of serverless application packages.
- **[AWS Service Catalog](https://blowstack.com/tools/cloud-services-hub/aws-service-catalog)**: Your VPC infrastructure can be delivered as Service Catalog products backed by CloudFormation templates. Administrators can offer approved network configurations with controlled subnet, routing, and security settings.
- **[AWS Shield](https://blowstack.com/tools/cloud-services-hub/aws-shield)**: Your VPC Elastic IP addresses can be registered for Shield Advanced protection. For supported EC2 protections, Shield Advanced can use associated network ACLs to help mitigate detected DDoS attacks.
- **[AWS Signer](https://blowstack.com/tools/cloud-services-hub/aws-signer)**: Your VPC can access AWS Signer APIs through an interface endpoint, allowing private signing-job and signing-profile operations.
- **[AWS Site-to-Site VPN](https://blowstack.com/tools/cloud-services-hub/aws-site-to-site-vpn)**: Your VPC can connect to an on-premises network through encrypted Site-to-Site VPN tunnels terminating on a virtual private gateway or transit gateway.
- **[AWS Snow Family](https://blowstack.com/tools/cloud-services-hub/aws-snow-family)**: Your VPC can access supported Snowball management APIs through an interface endpoint, allowing private management of Snow device jobs.
- **[AWS Step Functions](https://blowstack.com/tools/cloud-services-hub/aws-step-functions)**: Your VPC can access Step Functions through interface endpoints, allowing private workflow-management and execution requests.
- **[AWS Storage Gateway](https://blowstack.com/tools/cloud-services-hub/aws-storage-gateway)**: Your VPC can host an EC2-based Storage Gateway appliance and provide interface endpoints for supported gateway service communications. This allows supported gateway traffic to use private connectivity.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: Your VPC can provide interface endpoints for Systems Manager and its messaging services, enabling supported instance management without public service access. Automation runbooks can also inspect and change VPC networking resources.
- **[AWS Transfer Family](https://blowstack.com/tools/cloud-services-hub/aws-transfer-family)**: Your VPC can host Transfer Family server endpoints in selected subnets, with security groups controlling access. VPC-hosted endpoints can serve private clients or use supported internet-facing configurations.
- **[AWS Transit Gateway](https://blowstack.com/tools/cloud-services-hub/aws-transit-gateway)**: Your VPC can attach to a transit gateway through selected subnets, enabling centrally routed connectivity to other VPCs, VPN connections, and supported Direct Connect networks.
- **[AWS Trusted Advisor](https://blowstack.com/tools/cloud-services-hub/aws-trusted-advisor)**: Your VPC security groups and networking resources can be examined by Trusted Advisor checks. Recommendations can flag unrestricted access to sensitive ports and other supported networking risks.
- **[AWS User Notifications](https://blowstack.com/tools/cloud-services-hub/aws-user-notifications)**: Your VPC can access supported User Notifications APIs through interface endpoints, allowing private management of notification configurations and contacts.
- **[AWS Verified Access](https://blowstack.com/tools/cloud-services-hub/aws-verified-access)**: Your VPC can host private application backends exposed through Verified Access endpoints. Verified Access applies identity and device-context policies before allowing users to reach supported backend resources.
- **[AWS Wavelength](https://blowstack.com/tools/cloud-services-hub/aws-wavelength)**: Your VPC can extend into a Wavelength Zone through a Wavelength subnet. A carrier gateway provides supported connectivity between subnet resources and the telecommunications carrier network.
- **[AWS Well-Architected Tool](https://blowstack.com/tools/cloud-services-hub/aws-well-architected-tool)**: Your VPC can access Well-Architected Tool APIs through an interface endpoint, allowing private workload-review and milestone-management requests.
- **[AWS X-Ray](https://blowstack.com/tools/cloud-services-hub/aws-x-ray)**: Your VPC can use an X-Ray interface endpoint to submit trace data and access supported X-Ray APIs privately.
- **[EC2 Image Builder](https://blowstack.com/tools/cloud-services-hub/ec2-image-builder)**: Your VPC can host Image Builder build and test instances using subnets and security groups specified in an infrastructure configuration. Interface endpoints can provide private access to Image Builder and its required supporting services.
- **[Red Hat OpenShift Service on AWS (ROSA)](https://blowstack.com/tools/cloud-services-hub/red-hat-openshift-service-on-aws-(rosa))**: Your VPC supplies networking for ROSA clusters, including subnets, routing, and security controls. Supported private-cluster configurations keep application and management endpoints privately accessible.
- **[VMware Cloud on AWS](https://blowstack.com/tools/cloud-services-hub/vmware-cloud-on-aws)**: Your VPC can connect to a VMware Cloud on AWS software-defined data center through its connected-VPC configuration. Cross-account network interfaces provide private access between supported VMware workloads and resources in the connected VPC.

## Amazon VPC exam questions

Real practice exam questions on Amazon VPC, with the correct answer and its explanation.

### Question 1 (AIB-C01 (beta))

**Question:**

A healthcare company is moving an AI forecasting pilot into production on AWS. The application must query a database that will remain in the company's data center and has no public endpoint. A readiness review finds that the pilot's AWS network uses the same private IP address range as the data center. The data center's addressing cannot change. Leadership requires encrypted, privately addressed connectivity before production approval. Which infrastructure plan best meets these requirements?

**Correct answer:** Move the application into a new Amazon VPC with a non-overlapping address range, establish AWS Site-to-Site VPN connectivity, and configure routes and security controls for the required database traffic.

**Explanation:** A non-overlapping address plan enables unambiguous routing between AWS and the data center. Site-to-Site VPN provides encrypted connectivity using private addresses, while routes and security controls enable and restrict the required database access.

### Question 2 (MLA-C02 (beta))

**Question:**

A company runs a self-managed ML inference service on Amazon EC2 instances in a dedicated subnet. Application instances in subnet 10.40.2.0/24 initiate TCP connections to the inference service on port 8443, using client source ports 49152–65535. The inference instances must return prediction results over these connections but must not initiate any TCP connections to the application subnet, including connections to ports 49152–65535.

The inference instances have one security group that allows inbound TCP port 8443 from the application's security group and has no outbound rules. Routing is configured correctly, and the application subnet's security controls permit the required traffic. A new network ACL for the inference subnet will deny all traffic except explicitly allowed traffic.

Which configuration meets these requirements?

**Correct answer:** Keep the inference security group unchanged. Configure the inference subnet's network ACL to allow inbound TCP destination port 8443 from 10.40.2.0/24 and outbound TCP destination ports 49152–65535 to 10.40.2.0/24.

**Explanation:** The security group automatically permits responses to allowed inbound connections, even without outbound rules. Its lack of outbound rules prevents the inference instances from initiating new TCP connections. The stateless network ACL separately permits incoming requests to port 8443 and outgoing responses to the clients' ephemeral ports.

### Question 3 (SAP-C03)

**Question:**

A company uses AWS Organizations with AWS RAM organizational sharing enabled. A network account owns a customer-managed Amazon VPC prefix list containing approved service CIDR blocks. An application account references this prefix list in security group rules through an existing AWS RAM resource share that names the application account directly.

The company will divest the application account to another organization. Under a transition agreement, the application account must retain shared access to the same prefix list, receive subsequent prefix list updates, and remain able to create new security group rules that reference it. The existing share was created without retention enabled. All sharing changes and any required consumer acceptance must be completed before the account leaves, with no interruption in shared access. The prefix list supports sharing with external accounts, and applicable policies permit the arrangement.

Which solution meets these requirements?

**Correct answer:** Create a new resource share for the same prefix list with the application account ID as the principal. Set RetainSharingOnAccountLeaveOrganization to True and allowExternalPrincipals to True. Have the application account accept the invitation, verify access through the new share, and then remove the old share.

**Explanation:** A new account-to-account share configured with retention preserves the consumer's shared access after it leaves the organization. Retention requires allowExternalPrincipals to be True and triggers an invitation even for an account currently inside the organization. Accepting the new share before removing the old share maintains access to the same prefix list throughout the transition.

### Question 4 (SOA-C03)

**Question:**

A CloudOps engineer is provisioning EC2 worker instances that require IPv4 prefix delegation. Each worker's network interface requests one Amazon-provided /28 IPv4 prefix. Deployment fails with an InsufficientCidrBlocks error in a /24 subnet.

The subnet has 80 available IPv4 addresses, but existing network interfaces occupy addresses in every /28-aligned block. These interfaces must retain their current addresses. The VPC has unused IPv4 address space, and the workers can use a new subnet in the same Availability Zone. All required permissions and service quotas are sufficient.

Which action will resolve the deployment failure?

**Correct answer:** Create an empty /24 subnet in the same Availability Zone, create a prefix-type subnet CIDR reservation for an available /28 block, and deploy the workers into the new subnet.

**Explanation:** IPv4 prefix delegation requires a contiguous, correctly aligned /28 block. The new subnet provides unfragmented address space, and a prefix-type reservation protects the selected block from individual address assignments while making it available for prefix delegation.

### Question 5 (AIP-C01)

**Question:**

A company runs a foundation model inference worker on an Amazon EC2 instance. Incident responders discover that the worker is compromised and has established TCP connections to an internet command-and-control server through a NAT gateway and to a production database in another subnet of the same VPC.

The instance has one network interface and is the only resource in its subnet. The VPC uses IPv4 only. Its security group permits outbound traffic and permits inbound SSH from a dedicated forensic subnet. Forensic clients use source ports 1024–65535. Responders must immediately interrupt both established malicious connections, prevent their reestablishment, and preserve the ability to establish new SSH sessions from the forensic subnet. They must keep the instance running to collect volatile evidence.

Which action meets these requirements?

**Correct answer:** Associate the instance subnet with a custom network ACL that allows inbound TCP port 22 from the forensic subnet and outbound TCP ports 1024–65535 to that subnet, with all other traffic denied in both directions.

**Explanation:** Network ACLs are stateless and evaluate packets even for established connections. These rules interrupt the internet and database connections and prevent their reestablishment. The narrowly scoped inbound SSH and outbound client-port rules preserve new forensic SSH sessions, which the existing security group also permits. Because the instance is alone in its subnet, no same-subnet workload path bypasses this control.

### Question 6 (CLF-C02)

**Question:**

An Amazon EC2 worker in a private subnet submits jobs to an external processing service over HTTPS through a correctly configured public NAT gateway. The service immediately acknowledges each submission, but later attempts to open a new HTTPS connection to the worker to deliver the completed result. These delivery attempts fail. The worker must remain accessible only through private IP addresses, and no new inbound connectivity may be added. Which change will allow the worker to obtain completed results?

**Correct answer:** Configure the worker to periodically request completed results from the external service over HTTPS.

**Explanation:** The worker can initiate requests through the NAT gateway and receive results as response traffic. This avoids requiring the external service to initiate a new inbound connection to the worker.

### Question 7 (DEA-C01)

**Question:**

A company runs ingestion workers in private subnets in an Amazon VPC. The workers previously retrieved data from a partner's public database endpoint. Their outbound traffic passes through a public NAT gateway with private IPv4 address 10.20.1.10 and Elastic IP address 198.51.100.40.

The partner moves the database to private IPv4 address 172.30.4.25, reachable through an AWS Site-to-Site VPN connection attached to a transit gateway. The worker subnet route tables send traffic for the partner's network to the existing NAT gateway. The NAT gateway's subnet route table sends that traffic to the transit gateway, not to an internet gateway. All routes, return paths, security groups, and network ACLs are correctly configured.

The partner's firewall still allows database connections only from 198.51.100.40/32, so ingestion connections fail. The partner requires a single source IPv4 /32 entry that supports all workers, whose private addresses can change. Which source should replace the existing firewall allowlist entry?

**Correct answer:** 10.20.1.10/32, the NAT gateway's private IPv4 address

**Explanation:** When traffic from a public NAT gateway reaches a destination through a transit gateway rather than an internet gateway, the destination sees the NAT gateway's private IPv4 address. Allowlisting 10.20.1.10/32 therefore permits connections from all workers using this path despite changes to their individual addresses.

### Question 8 (SCS-C03)

**Question:**

A company exposes an HTTPS API through an AWS PrivateLink endpoint service backed by an internal Network Load Balancer (NLB). The company approves each consumer's endpoint connection, and the API independently authenticates and authorizes every request.

The NLB has a security group that allows inbound TCP port 443 only from a provider monitoring subnet. Direct connections to the NLB must remain restricted to that subnet. The API targets' security group allows application traffic only from the NLB security group.

New consumers have interface endpoints with security groups that permit HTTPS from their application workloads. However, their connections time out because the NLB currently enforces its inbound security group rules on PrivateLink traffic. The company must support approved consumers without collecting or allowlisting their application IP address ranges and without broadening direct access to the NLB.

Which change meets these requirements?

**Correct answer:** Turn off enforcement of the NLB's inbound security group rules for PrivateLink traffic. Retain the existing NLB inbound rules and the targets' rule that permits application traffic only from the NLB security group.

**Explanation:** An NLB can bypass inbound security group rule evaluation specifically for PrivateLink traffic. Direct traffic remains subject to the existing monitoring-subnet restriction. Endpoint connection approval, consumer endpoint security groups, and application authentication continue to control consumer access, while the target security group prevents direct access to the API targets.

### Question 9 (DVA-C02)

**Question:**

An AWS Lambda function must call a private HTTPS service in a peered VPC. The Lambda VPC has CIDR block 10.10.0.0/16, and the service VPC has CIDR block 10.20.0.0/16. The VPC peering connection is active, and the service subnet has a return route for 10.10.0.0/16 through the peering connection. Security groups and network ACLs allow the required traffic, and DNS resolves the service hostname to its private IP address.

The developer tests the function with each of two Lambda subnets separately:
• Subnet A uses a custom route table containing the VPC local route and a route for 10.20.0.0/16 through the peering connection. Calls succeed.
• Subnet B has no explicit route table association and uses the main route table, which contains only the VPC local route. Calls time out.

The function must use both subnets. The developer must restore connectivity without changing routing for other subnets that use the main route table. Which change meets these requirements?

**Correct answer:** Explicitly associate Subnet B with the custom route table that Subnet A uses.

**Explanation:** A subnet without an explicit association uses the VPC's main route table. Associating Subnet B with the existing custom route table gives it the required route through the peering connection without changing routing for other subnets using the main route table.

### Question 10 (DOP-C02)

**Question:**

A company delivers VPC Flow Logs to an Amazon CloudWatch Logs log group in us-east-1. Security policy requires the log group to use a particular customer managed AWS KMS key. Delivery worked before a DevOps engineer associated this key with the log group, but new records are no longer arriving after the association has fully propagated.

The flow log's delivery role trusts vpc-flow-logs.amazonaws.com and has the required CloudWatch Logs permissions. The KMS key is enabled, is in us-east-1, and has a key policy that currently grants access only to key administrators. There are no applicable explicit denies.

The engineer must restore delivery while restricting cryptographic use of the key to the designated log group. Which change meets these requirements?

**Correct answer:** Update the KMS key policy to allow logs.us-east-1.amazonaws.com to perform the required KMS cryptographic operations, with an ArnEquals condition on kms:EncryptionContext:aws:logs:arn matching the designated log group ARN.

**Explanation:** CloudWatch Logs uses its regional service principal to encrypt log data with the associated KMS key. The key policy must authorize that principal for operations such as Encrypt, Decrypt, ReEncrypt, GenerateDataKey, and DescribeKey. Restricting kms:EncryptionContext:aws:logs:arn to the designated log group ARN limits cryptographic use to that log group. The existing flow log delivery role does not need to be replaced.

### Question 11 (SAA-C03)

**Question:**

A company already provides employees with encrypted remote access to its corporate network through an on-premises remote-access gateway. The corporate network connects to a single VPC through an existing BGP-based AWS Site-to-Site VPN connection. Both connections have sufficient unused capacity.

Ten administrators now need to access private IP addresses of EC2 instances in the VPC from their laptops. Their remote-access address pool does not overlap with the corporate network or VPC CIDR blocks. Currently, the remote-access gateway does not forward traffic to the VPC, and the corporate router does not advertise the remote-access address pool to AWS. Company policy permits forwarding this traffic through the corporate network, and the resulting latency is acceptable.

Which solution provides encrypted connectivity with the LOWEST additional fixed AWS connectivity charges?

**Correct answer:** Configure the remote-access gateway to forward VPC-bound traffic to the corporate router. Advertise the remote-access address pool over the existing BGP sessions, ensure VPC return routes use the existing VPN, and permit the traffic in the relevant security controls.

**Explanation:** The administrators can use the existing encrypted remote-access connection to reach the corporate network and the existing encrypted Site-to-Site VPN to reach AWS. Forwarding, destination routes, return routes, and security permissions complete the path. Because both connections have spare capacity, this solution requires no additional fixed AWS connectivity charges.

### Question 12 (ANS-C01)

**Question:**

During a network containment audit, a company tests whether it can immediately stop HTTPS communication from EC2 instances in a dedicated subnet to a compromised external IPv4 address. An instance has an established TCP connection from local port 55000 to port 443 on that address. The connection is tracked by its security group.

The security group permits outbound TCP port 443 to the external address and has no inbound rules. The subnet's network ACL has rule 100 allowing all IPv4 traffic in each direction, followed by the default deny. No other security groups are attached.

The audit requires a control that stops both existing and newly initiated HTTPS connections to the compromised address without interrupting traffic to other external addresses. The validation must demonstrate containment of the existing connection, not merely failure of a new connection attempt.

Which action meets these requirements?

**Correct answer:** Add network ACL rule 50 in each direction to deny all TCP traffic to or from the compromised address's /32 CIDR. Validate that the existing connection stops transferring application data and that new HTTPS connections fail.

**Explanation:** Network ACLs evaluate packets independently of security group connection state. Inbound and outbound denies for the specific /32, evaluated before rule 100, block packets belonging to both existing and new connections. Other external addresses remain unaffected. Testing the established session and a new connection provides evidence of both containment requirements.

## Practice Amazon VPC in a full exam

Questions on Amazon VPC in each practice exam, with every answer option and an explanation for each:

- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 187 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 107 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 84 questions
- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 48 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 36 questions
- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 28 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 22 questions
- [MLA-C02 (beta)](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate): 14 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 14 questions
- [AIP-C01](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional): 8 questions
- [DVA-C02](https://blowstack.com/practice-exams/aws-certified-developer-associate): 4 questions
- [AIB-C01 (beta)](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist): 3 questions
- [AIF-C01](https://blowstack.com/practice-exams/aws-certified-ai-practitioner): 1 question

## What is Amazon VPC

Amazon Virtual Private Cloud (Amazon VPC) stands as a cornerstone service within the Amazon Web Services (AWS) offering, empowering users to provision a logically isolated section of the Amazon Web Cloud. This functionality is invaluable for businesses and developers aiming to launch and manage their applications in a secured, scalable, and highly customizable virtual networking environment.

Amazon VPC lets customers dive into cloud computing while retaining a granular level of control over their virtual networking environment. This includes the selection of IP address ranges, creation of subnets, and configuration of route tables and network gateways. The heart of Amazon VPC lies in its ability to offer enhanced security. By enabling users to define a virtual network in their own logically isolated area within the AWS ecosystem, it ensures that access to resources is tightly regulated. Security groups provide stateful traffic filtering at the instance level, while network access control lists provide stateless filtering at the subnet level.

VPC Encryption Controls centrally monitor and enforce traffic encryption within and across VPCs in a Region. Monitor mode identifies non-compliant resources and adds encryption status to VPC flow logs; enforce mode prevents creation or attachment of resources that allow unencrypted traffic within the VPC boundary.

The default quota is five IPv4 CIDR blocks per VPC, counting the primary and all secondary blocks; it can be increased to 50.

VPC IP Address Manager (IPAM) helps plan, track, and monitor IP addresses. Its Free Tier supports IP address management in a single AWS Region and account, including BYOIP and Amazon-provided contiguous IPv6 addresses. Its Advanced Tier supports management across multiple Regions or accounts and adds capabilities such as private IPv4 management and IP history auditing.

Amazon-provided contiguous IPv4 blocks provide sequential public IPv4 addresses to simplify networking and security allowlisting.

Furthermore, the option to connect a VPC to one's own corporate data center via an industry-standard encrypted IPsec VPN connection enhances the allure for enterprises looking to adopt a hybrid cloud approach. Besides security, the Amazon VPC architecture is meticulously designed for high availability and scalability. With the provision to create multiple subnets within a VPC across different Availability Zones, it ensures that applications remain resilient in the face of data center failures, thereby promoting high availability and fault tolerance.

Each subnet must reside in a single Availability Zone.

NAT Gateways also support a regional availability mode: a single gateway automatically expands and contracts across Availability Zones in the VPC based on workload presence.

Scalability, another key facet, is addressed through the ability to start with a modestly sized network and expand as needed. This flexibility makes it an attractive proposition for startups and large enterprises alike. Networking features within Amazon VPC also include the ability to create a public-facing subnet for internet-facing resources like web servers, while maintaining backend systems such as databases or application servers in a private-facing subnet with no internet access. This separation further enhances the security and efficiency of operations within the cloud. Amazon VPCs integration with other Amazon Web Services is seamless, facilitating a comprehensive and robust ecosystem for deploying applications.

Services such as Amazon EC2 instances can be securely tucked within a VPC, bolstering the networking functionality with the computational prowess of AWS. The ease of connecting VPCs across different regions to share resources securely, known as VPC peering, extends the capabilities of global enterprises by allowing them to operate in a globally distributed fashion.

In essence, Amazon VPC is not just a feature of AWS; it represents a foundational component that encapsulates the essence of cloud computing - security, scalability, and flexibility. It provides businesses the tools and confidence to build sophisticated applications in the cloud, ensuring that their network architecture can support the demanding needs of todayâs IT environments.

## Learn Amazon VPC in lessons

34 short lessons on Amazon VPC in 11 certification courses.

- AIB-C01 (beta): Amazon VPC: workload isolation and connectivity (Premium), https://app.blowstack.com/lessons/amazon-vpc-workload-isolation-and-connectivity-aib-c01
- MLA-C02 (beta): Amazon VPC: private subnet networking (Premium), https://app.blowstack.com/lessons/amazon-vpc-private-subnet-networking-mla-c02
- SAP-C03: Amazon VPC: address planning and subnet segmentation (Premium), https://app.blowstack.com/lessons/amazon-vpc-address-planning-and-subnet-segmentation-sap-c03
- AIF-C01: Amazon VPC: network isolation (Premium), https://app.blowstack.com/lessons/amazon-vpc-network-isolation-aif-c01
- SOA-C03: AWS PrivateLink vs Amazon VPC: service access or VPC peering (Premium), https://app.blowstack.com/lessons/aws-privatelink-vs-amazon-vpc-service-access-or-vpc-peering-soa-c03
- AIP-C01: Amazon VPC: isolated service access through VPC endpoints (Premium), https://app.blowstack.com/lessons/amazon-vpc-isolated-service-access-through-vpc-endpoints-aip-c01

## Concepts related to Amazon VPC

- [IP Routing](https://blowstack.com/tools/cloud-concepts-hub/ip-routing): IP routing is the process of selecting paths and forwarding Internet Protocol packets between networks using destination addresses and routing information.
- [Stateful and Stateless Filtering](https://blowstack.com/tools/cloud-concepts-hub/stateful-and-stateless-filtering): Stateful and stateless filtering are approaches to permitting or blocking network packets based on either tracked connection context or independent packet-by-packet rules.
- [IP Addressing](https://blowstack.com/tools/cloud-concepts-hub/ip-addressing): IP addressing is the system of assigning logical network addresses to interfaces so that devices and services can identify endpoints and route traffic between networks.
- [Network Segmentation](https://blowstack.com/tools/cloud-concepts-hub/network-segmentation): Network segmentation divides a network into distinct zones and controls communication between them according to security requirements.
- [Network Address Translation](https://blowstack.com/tools/cloud-concepts-hub/network-address-translation): Network Address Translation rewrites IP addresses, and sometimes transport-layer ports, as packets move between networks.
- [Network Isolation](https://blowstack.com/tools/cloud-concepts-hub/network-isolation): Network isolation separates resources and restricts their communication to prevent unauthorized access and limit the spread of security incidents.
- [Classless Inter-Domain Routing (CIDR)](https://blowstack.com/tools/cloud-concepts-hub/classless-inter-domain-routing-(cidr)): Classless Inter-Domain Routing (CIDR) represents IP address ranges using an address and prefix length, enabling flexible subnet allocation and route aggregation without fixed address classes.
- [Defense in Depth](https://blowstack.com/tools/cloud-concepts-hub/defense-in-depth): Defense in Depth is a security strategy that uses multiple complementary layers of protection so that failure of one control does not expose the entire system.
- [Capacity Planning](https://blowstack.com/tools/cloud-concepts-hub/capacity-planning): Capacity planning is the process of estimating workload demand and arranging sufficient resources to meet performance, growth, and resilience requirements within cost constraints.
- [Network Peering](https://blowstack.com/tools/cloud-concepts-hub/network-peering): Network peering connects independently managed networks so their resources can communicate through explicitly configured routes and access controls.
- [Attack Surface Reduction](https://blowstack.com/tools/cloud-concepts-hub/attack-surface-reduction): Attack Surface Reduction is the practice of removing unnecessary entry points and access paths that attackers could use to reach or compromise systems.
- [Hub-and-Spoke Topology](https://blowstack.com/tools/cloud-concepts-hub/hub-and-spoke-topology): Hub-and-spoke topology is a network design in which multiple peripheral networks connect to a central hub that controls connectivity between them and shared destinations.
- [Data Egress](https://blowstack.com/tools/cloud-concepts-hub/data-egress): Data egress is the transfer of data out of a defined boundary, such as a cloud service, network, Region, or cloud provider.
- [Subnetting](https://blowstack.com/tools/cloud-concepts-hub/subnetting): Subnetting divides an IP address block into smaller, non-overlapping networks to organize address allocation, routing, and connectivity boundaries.
- [Asymmetric Routing](https://blowstack.com/tools/cloud-concepts-hub/asymmetric-routing): Asymmetric routing occurs when traffic traveling from a source to a destination follows a different network path from the return traffic.
- [Blast Radius](https://blowstack.com/tools/cloud-concepts-hub/blast-radius): Blast radius is the extent of resources, identities, data, and business functions that a failure, compromise, or erroneous change can affect.
- [Dual-Stack Networking](https://blowstack.com/tools/cloud-concepts-hub/dual-stack-networking): Dual-stack networking is the simultaneous operation of IPv4 and IPv6 within the same network environment so applications can communicate using either protocol.
- [Ephemeral Ports](https://blowstack.com/tools/cloud-concepts-hub/ephemeral-ports): Ephemeral ports are temporary TCP or UDP port numbers typically assigned to applications when they initiate network communication.
- [Multi-Tier Architecture](https://blowstack.com/tools/cloud-concepts-hub/multi-tier-architecture): Multi-tier architecture separates an application into independently deployed tiers with distinct responsibilities and controlled network communication.
- [Trust Boundaries](https://blowstack.com/tools/cloud-concepts-hub/trust-boundaries): Trust boundaries are points where data, requests, or identities cross between environments with different security assumptions or levels of control.
- [IPv6](https://blowstack.com/tools/cloud-concepts-hub/ipv6): IPv6 is the version of the Internet Protocol that uses 128-bit addresses to identify network interfaces and route packets across interconnected networks.
- [Lateral Movement](https://blowstack.com/tools/cloud-concepts-hub/lateral-movement): Lateral movement is an attacker’s progression from an initial foothold to other systems, identities, or resources within an environment.
- [Longest Prefix Match](https://blowstack.com/tools/cloud-concepts-hub/longest-prefix-match): Longest Prefix Match is the routing rule that selects the matching destination prefix with the greatest number of network bits.
- [Networking, connectivity, and content delivery](https://blowstack.com/tools/cloud-concepts-hub/networking-connectivity-and-content-delivery): Networking, connectivity, and content delivery is the design of communication paths that connect cloud resources, users, and external networks while delivering application traffic efficiently and securely.
- [Parameterization](https://blowstack.com/tools/cloud-concepts-hub/parameterization): Parameterization separates environment-specific values from reusable infrastructure definitions by supplying those values through explicit inputs.
- [Maximum Transmission Unit](https://blowstack.com/tools/cloud-concepts-hub/maximum-transmission-unit): Maximum Transmission Unit (MTU) is the largest network-layer packet, measured in bytes, that a link or interface can carry without fragmentation.
- [Packet Loss](https://blowstack.com/tools/cloud-concepts-hub/packet-loss): Packet loss is the failure of transmitted network packets to reach their intended destination.
- [Path MTU Discovery](https://blowstack.com/tools/cloud-concepts-hub/path-mtu-discovery): Path MTU Discovery determines the largest IP packet that can traverse a network path without fragmentation.
- [DHCP](https://blowstack.com/tools/cloud-concepts-hub/dhcp): DHCP, the Dynamic Host Configuration Protocol, automatically supplies hosts with IP addressing and other network settings through renewable leases.
- [GENEVE](https://blowstack.com/tools/cloud-concepts-hub/geneve): GENEVE is an extensible UDP-based encapsulation protocol that carries network traffic and metadata across an underlying IP network.
- [IGMP](https://blowstack.com/tools/cloud-concepts-hub/igmp): IGMP is the IPv4 control protocol that hosts and adjacent multicast routers use to manage multicast group membership.
- [Multicast](https://blowstack.com/tools/cloud-concepts-hub/multicast): Multicast is a network delivery method that sends packets to a group address so the network can distribute copies to participating receivers.
- [OSI Model](https://blowstack.com/tools/cloud-concepts-hub/osi-model): The OSI Model is a seven-layer reference framework for understanding how networked systems exchange data, from physical transmission to application protocols.
- [Route Summarization](https://blowstack.com/tools/cloud-concepts-hub/route-summarization): Route summarization combines multiple more-specific IP routes into a broader CIDR prefix to reduce routing information while preserving intended reachability.
- [Transitive Routing](https://blowstack.com/tools/cloud-concepts-hub/transitive-routing): Transitive routing allows traffic between two networks to pass through an intermediate network or routing hub rather than requiring a direct connection.
- [Virtual Private Networks](https://blowstack.com/tools/cloud-concepts-hub/virtual-private-networks): Virtual private networks (VPNs) create logically private connections across an underlying network, commonly using encrypted tunnels to protect traffic.
- [Dependency Mapping](https://blowstack.com/tools/cloud-concepts-hub/dependency-mapping): Dependency mapping identifies and documents the relationships that applications, infrastructure, data, and operational processes rely on to function.
- [DNS Tunneling](https://blowstack.com/tools/cloud-concepts-hub/dns-tunneling): DNS tunneling carries non-DNS data inside DNS queries and responses, creating a communication channel through name-resolution infrastructure.
- [Environment Isolation](https://blowstack.com/tools/cloud-concepts-hub/environment-isolation): Environment isolation separates development, testing, staging, and production resources so that activity in one environment does not unintentionally affect another.
- [Ethernet Switching](https://blowstack.com/tools/cloud-concepts-hub/ethernet-switching): Ethernet switching forwards Ethernet frames within a Layer 2 network using destination MAC addresses and VLAN membership.
- [Public Cloud](https://blowstack.com/tools/cloud-concepts-hub/public-cloud): Public cloud is a deployment model in which a third-party provider offers computing resources for use by many customers on provider-operated infrastructure.
- [Static Routing](https://blowstack.com/tools/cloud-concepts-hub/static-routing): Static routing directs network traffic using explicitly configured destination-to-next-hop mappings rather than routes learned through a dynamic routing protocol.
- [Transmission Control Protocol](https://blowstack.com/tools/cloud-concepts-hub/transmission-control-protocol): Transmission Control Protocol (TCP) is a connection-oriented transport protocol that provides applications with a reliable, ordered byte stream over IP networks.
- [Unicast](https://blowstack.com/tools/cloud-concepts-hub/unicast): Unicast is a network delivery method in which a sender addresses each packet to one destination rather than to a group of receivers.
- [Virtualization](https://blowstack.com/tools/cloud-concepts-hub/virtualization): Virtualization abstracts physical computing resources into logical resources, allowing isolated environments to share underlying hardware.
