Amazon Virtual Private Cloud (Amazon VPC) lets you provision a logically isolated section of the Amazon Web Services (AWS) Cloud where you can launch AWS resources in a virtual network that you define. You have complete control over your virtual networking environment, including selection of your own IP address range, creation of subnets, and configuration of route tables and network gateways.
You can easily customize the network configuration for your Amazon VPC. For example, you can create a public-facing subnet for your webservers that has access to the Internet, and place your backend systems such as databases or application servers in a private-facing subnet with no Internet access. You can leverage multiple layers of security, including security groups and network access control lists, to help control access to Amazon EC2 instances in each subnet.
Additionally, you can create a Hardware Virtual Private Network (VPN) connection between your corporate datacenter and your VPC and leverage the AWS cloud as an extension of your corporate datacenter.1
Table of contents
- Amazon Virtual Private Cloud Getting Started Guide - Provides a hands-on introduction to Amazon VPC.
- Amazon Virtual Private Cloud User Guide - Provides detailed information about how to use Amazon VPC.
- Amazon Virtual Private Cloud Network Administrator Guide - Helps network administrators configure your customer gateway.
- What is Amazon VPC? Amazon Virtual Private Cloud (Amazon VPC) enables you to launch Amazon Web Services (AWS) resources into a virtual network that you've defined. This virtual network closely resembles a traditional network that you'd operate in your own data center, with the benefits of using the scalable infrastructure of AWS.
- Benefits of Using a VPC
Scenarios for Amazon VPC2
- http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenario1.html Scenario 1: VPC with a Public Subnet Only - Run a single-tier, public-facing web application such as a blog or simple web site.
- http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenario2.html Scenario 2: VPC with Public and Private Subnets -Run a public-facing web application, while still maintaining non-publicly accessible back-end servers in a second subnet.
- http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenario3.html Scenario 3: VPC with Public and Private Subnets and Hardware VPN Access - Extend your data center into the cloud, and also directly access the Internet from your VPC.
- http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenario4.html Scenario 4: VPC with a Private Subnet Only and Hardware VPN Access - Extend your data center into the cloud, and leverage Amazon's infrastructure without exposing your network to the Internet.
- 25 Best Practice Tips for architecting your Amazon VPC
- VPC Best Configuration Practices
- Amazon AWS Best practices - Enterprise Perspective