From efca6b0e8ae41b13f7984bd9e2f6c2ee98a37d7b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=B6ren=20Blom?= Date: Wed, 7 Jan 2015 12:52:20 +0100 Subject: [PATCH] only non-default VPC security groups are referenced by ID. --- website/source/docs/providers/aws/r/instance.html.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/docs/providers/aws/r/instance.html.markdown b/website/source/docs/providers/aws/r/instance.html.markdown index 66d9c9caca..25e6cfe366 100644 --- a/website/source/docs/providers/aws/r/instance.html.markdown +++ b/website/source/docs/providers/aws/r/instance.html.markdown @@ -35,8 +35,8 @@ The following arguments are supported: * `instance_type` - (Required) The type of instance to start * `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. - If you are within a VPC, you'll need to use the security group ID. Otherwise, - for EC2, use the security group name. + If you are within a non-default VPC, you'll need to use the security group ID. Otherwise, + for EC2 and the default VPC, use the security group name. * `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. * `private_ip` - (Optional) Private IP address to associate with the