only non-default VPC security groups are referenced by ID.

This commit is contained in:
Sören Blom 2015-01-07 12:52:20 +01:00
parent 2203ef82a4
commit efca6b0e8a
1 changed files with 2 additions and 2 deletions

View File

@ -35,8 +35,8 @@ The following arguments are supported:
* `instance_type` - (Required) The type of instance to start * `instance_type` - (Required) The type of instance to start
* `key_name` - (Optional) The key name to use for the instance. * `key_name` - (Optional) The key name to use for the instance.
* `security_groups` - (Optional) A list of security group IDs or names to associate with. * `security_groups` - (Optional) A list of security group IDs or names to associate with.
If you are within a VPC, you'll need to use the security group ID. Otherwise, If you are within a non-default VPC, you'll need to use the security group ID. Otherwise,
for EC2, use the security group name. for EC2 and the default VPC, use the security group name.
* `subnet_id` - (Optional) The VPC Subnet ID to launch in. * `subnet_id` - (Optional) The VPC Subnet ID to launch in.
* `associate_public_ip_address` - (Optional) Associate a public ip address with an instance in a VPC. * `associate_public_ip_address` - (Optional) Associate a public ip address with an instance in a VPC.
* `private_ip` - (Optional) Private IP address to associate with the * `private_ip` - (Optional) Private IP address to associate with the