Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and HP Cloud Services or Amazon EC2

Appendix: Provisioning to an Amazon VPC

CloudSystem can provision instances to an Amazon VPC in a manner similar to EC2.

 A VPC must be pre-provisioned, with subnets, gateways, and routing tables configured as necessary. (See

Amazon Virtual Private Cloud FAQs.)

 A single cloud capacity pool can be used to provision to EC2 or to a specified VPC, but not both. A capacity

pool can be targeted to a VPC instead of an EC2 region by setting, for example, provider.vpc.id=vpc-

1a2b3c4d in the EC2 capacity pool configuration.

 Available VPC subnets are represented in the IO subnet inventory using their native subnet ID (for example,

subnet-1a2b3c4d). They must be configured for use in IO by setting a DNS domain and a DHCP address

range.

Limitations

Note the following limitations when provisioning to an Amazon VPC. For more information, and for planning, design,

and implementation services, contact HP Technology Services at www.hp.com/services/cloud.

 An instance provisioned to a VPC is not assigned a public IP address and is therefore not accessible over the

Internet. If Internet access is required, an external integration may be used to attach an Elastic IP address. You

can also add an Elastic IP address using infrastructure orchestration. Select “Manage floating IPs” from the

Server Actions list on the Services tab, or use the Matrix API or CLI. For more information, see Create a new

service using the template.

 An instance may be provisioned in a VPC with one or two subnet connections. The default security group is used

for a second subnet connection, and IO cannot configure or alter it. An external integration may be required to

change this security group setting.

 The first network interface in the IO template must be marked as primary.