         | Did this page help you? Yes No Tell us about it... |
Where Do You Go From Here?
Topics
If you stepped through the preceding example, you've set up a VPC and launched an instance into it. Where do you go from here? This section describes other information you need to know about using Amazon VPC.
Optional Next Step: Deleting the VPC
If you completed the exercise in this guide, then you have a VPC with an Internet gateway and a running instance. If you'd like, you can keep the VPC and continue working with it. Or you might want to try another one of the options the Amazon VPC wizard offers.
If you'd like to delete the VPC, you must terminate the instance, and then delete the VPC and all of its related components (the Elastic IP address, the running instance, the security group, the subnet, and the Internet gateway).
To delete your VPC
On the Amazon EC2 tab of the console, go to the Instances page.
Right-click the instance running in the VPC and select Terminate.
A confirmation dialog box appears.
Click Yes, Terminate.
On the Amazon VPC tab of the console, go to the Your VPC page.
Select the VPC and click Delete.
A confirmation dialog box appears.
Click Yes, Delete.
We begin deleting your VPC and its components. The dialog box displays the progress of the deletion.
you can manually create a new VPC or use one of the other options in the Amazon VPC wizard to create a new VPC. To get information about the other wizard options, see the next section.
Other Scenarios for Using Amazon VPC
This guide presents a simple scenario for using Amazon VPC. There might be others that fit your needs better. Following is a summary of the scenarios we cover in the Amazon VPC technical documentation and in the wizard. For a detailed discussion of the other scenarios, go to Amazon Virtual Private Cloud User Guide.
![[Note]](http://docs.amazonwebservices.com/docs-common/images/note.png) | Note |
|---|---|
The following scenarios are common ones we chose to present; you can configure subnets and other Amazon VPC components in other ways to suit your needs. |
Scenario 1: VPC with a Public Subnet Only
We recommend this scenario if you want to run a single-tier, public-facing web application such as a blog or simple website.
This is the scenario covered in the exercise in this guide. For a more detailed discussion, go to Scenario 1: VPC with a Single Public Subnet Only in the Amazon Virtual Private Cloud User Guide.
Scenario 2: VPC with Public and Private Subnets
We recommend this scenario if you want to run a public-facing web application while still maintaining non-publicly accessible backend servers in a second subnet.
For more information, go to Scenario 2: VPC with Public and Private Subnets in the Amazon Virtual Private Cloud User Guide.
Scenario 3: VPC with Public and Private Subnets and Hardware VPN Access
We recommend this scenario if you want to extend your data center into the cloud and also directly access the Internet from your VPC. This scenario requires you to configure a gateway appliance in your home network to establish a VPN connection to the VPC.
For more information, go to Scenario 3: VPC with Public and Private Subnets and VPN Access in the Amazon Virtual Private Cloud User Guide.
Scenario 4: VPC with a Private Subnet Only and Hardware VPN Access
We recommend this scenario if you want to extend your data center into the cloud and leverage Amazon's elasticity without exposing your network to the Internet. This scenario requires you to configure a gateway appliance in your home network to establish a VPN connection to the VPC.
For more information, go to Scenario 4: VPC with a Private Subnet Only and VPN Access in the Amazon Virtual Private Cloud User Guide.
Current Service Limitations
With the current implementation of Amazon VPC:
You can have up to five (5) VPCs per account per Region.
You can have up to five (5) Amazon VPC Elastic IP Addresses per AWS account per Region.
You can create up to twenty (20) subnets per Amazon VPC.
Once you create a VPC or subnet, you can't change its IP address range.
If you plan to have a VPN connection to your VPC, then you can have up to five virtual private gateways per AWS account per Region (one per VPC), with up to ten VPN connections per virtual private gateway.
You can't use either broadcast or multicast within your VPC.
Cluster Instances and Micro Instances do not work with a VPC.
AWS Elastic Beanstalk is not available with your instances in a VPC.
Amazon DevPay paid AMIs do not work with a VPC.
For more information about VPC limits, see Appendix B: Limits in the Amazon Virtual Private Cloud User Guide.
Other Ways to Access Amazon VPC
This guide has shown you how to use Amazon VPC through the AWS Management Console. You can continue using the service through the console, or you can try one of the other interfaces.
Continue Using the Console
To learn more about how to use Amazon VPC through the console, go to the Amazon Virtual Private Cloud User Guide. The console also has online Help to assist you (just click the Help button in the console).
Use the Command Line Interface
Amazon EC2 and Amazon VPC share a Java-based command line interface. These command line tools are a fast way to execute all the Amazon EC2 and Amazon VPC functions without coding to the API or using a library. For information about getting started with the command line tools, go to Getting Started with the Command Line Tools in the Amazon Elastic Compute Cloud User Guide. For a complete description of all the commands, go to the Amazon Elastic Compute Cloud Command Line Reference.
Use an Existing Library
Amazon EC2 and Amazon VPC share the same programmatic interface. If you prefer to use Amazon VPC through an API, there are libraries and resources available for the following languages:
For libraries and sample code in all languages, go to Amazon EC2 Sample Code & Libraries.
Code Directly to the Web Service API
If you want to write code directly to the Amazon EC2 and VPC API, go to Making API Requests in the Amazon Elastic Compute Cloud User Guide. The guide describes how to create and authenticate API requests, and how to use Amazon EC2 and Amazon VPC through the APIs. For a complete description of all the API actions, go to the Amazon Elastic Compute Cloud API Reference.
AWS Account and Security Credentials
This guide walked you through signing up for the service, getting an AWS account, and then completing a short exercise. Now that you've completed the exercise, we recommend you check with an administrator or co-worker in your organization to determine if they already have an AWS account and security credentials for you to use in future interactions with AWS.
If you're an account owner or administrator and would like to know more about AWS Identity and Access Management, go to http://aws.amazon.com/iam and to Using AWS Identity and Access Management.
Supporting Documentation
This Getting Started Guide covers the basic commands you can use with Amazon VPC. The following table summarizes the other available documentation for Amazon VPC.
| Description | Documentation |
|---|---|
|
Complete discussion of how to use Amazon VPC | |
|
Information about configuring the customer gateway (if you decide to use a VPN connection with your VPC) | |
|
A hands-on introduction to Amazon EC2 | |
|
Complete discussion of how to use Amazon EC2 | |
|
Complete descriptions of all the Amazon VPC and Amazon EC2 commands | |
|
Quick reference descriptions of the commonly used Amazon VPC commands | |
|
Complete descriptions of the Amazon VPC and Amazon EC2 API operations, data types, and errors |
Where to Get Additional Help
We recommend that you take advantage of the AWS Discussion Forums. These are community-based forums for users to discuss technical questions related to AWS services. For the Amazon VPC forum, go to https://forums.aws.amazon.com/forum.jspa?forumID=58.
You can also get help if you subscribe to AWS Premium Support, a one-on-one, fast-response support channel (for more information, go to http://aws.amazon.com/premiumsupport).
