Using Amazon Virtual Private Cloud

Amazon Elastic Compute Cloud: 2009-07-15

previous page next page

Using Amazon Virtual Private Cloud

Topics

Procedure
  • Related Topics

    • Amazon Virtual Private Cloud enables you to designate your own private resources within the AWS cloud, and then connect those resources directly to your own data center using a VPN connection. With regards to Amazon EC2, this mean you can launch instances in your Amazon VPC virtual private cloud (VPC), and those instances are isolated from compute capacity being used by other EC2 users. You can also separate the instances into different subnets to provide network isolation of the instances within your private VPC.

    This section describes how to launch instances into a VPC that you've created. For detailed information about Amazon VPC and creating a VPC and subnets, go to the Amazon Virtual Private Cloud Getting Started Guide.

    Procedure

    To launch an instance in a VPC

    1. If you are using SOAP, construct the following request, with the ID of the Amazon VPC subnet where you want the instance launched:

      <RunInstances xmlns="http://ec2.amazonaws.com/doc/2009-07-15/">
   <imageId>ami-id</imageId>
   <minCount>1</minCount>
   <maxCount>1</maxCount>
   <keyName>keypair-name</keyName>
   <groupSet/>
   <monitoring/>
   <subnetId>subnet-id</subnetId>
</RunInstances>

    2. If you are using Query, construct the following request, with the ID of the Amazon VPC subnet where you want the instance launched:

      https://ec2.amazonaws.com/
?Action=RunInstances
&ImageId=ami-id
&MaxCount=1
&MinCount=1
&KeyName=keypair-name
&SubnetId=subnet-id
&...auth parameters...

    3. View output similar to the following: 

      <RunInstancesResponse xmlns="http://ec2.amazonaws.com/doc/2009-07-15/">
<reservationId>r-47a5402e</reservationId>
<ownerId>AIDADH4IGTRXXKCD</ownerId>
  <groupSet/>
  <instancesSet>
    <item>
      <instanceId>i-2ba64342</instanceId>
      <imageId>ami-60a54009</imageId>
      <instanceState>
        <code>0</code>
        <name>pending</name>
      </instanceState>
      <privateDnsName></privateDnsName>
      <dnsName></dnsName>
      <keyName>example-key-name</keyName>
      <amiLaunchIndex>0</amiLaunchIndex>
      <instanceType>m1.small</instanceType>
      <launchTime>2009-08-07T11:51:50.000Z</launchTime>
      <placement>
        <availabilityZone>us-east-1b</availabilityZone>
      </placement>
      <monitoring>
        <enabled>false</enabled>
      </monitoring>
      <subnetId>subnet-1a2b3d4d</subnetId>
      <vpcId>vpc-6e7f8a92</vpcId>
      <privateIpAddress>10.0.0.1</privateIpAddress>
      <ipAddress></ipAddress>
    </item>
  </instancesSet>
</RunInstancesResponse>

    Each instance you launch in a VPC is assigned a private IP address within the range of IP addresses you specified when you created the subnet. The instance has no public IP address or DNS names. For information about programmatically creating a VPC and subnets, go to the Amazon Virtual Private Cloud Developer Guide.

    [Important] Important

    After launching an instance, you are billed hourly for running time. When you are finished, make sure to terminate any instances that you started.
    previous page start next page