From 2e1f18b10a373c99fbc9cf3ae19fa0c837635cda Mon Sep 17 00:00:00 2001 From: Prashant Kandathil Date: Thu, 26 Jan 2017 16:03:57 -0800 Subject: [PATCH] Update build-image.html.md --- website/source/intro/getting-started/build-image.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/intro/getting-started/build-image.html.md b/website/source/intro/getting-started/build-image.html.md index 4d2f6ff70..c75df4e0b 100644 --- a/website/source/intro/getting-started/build-image.html.md +++ b/website/source/intro/getting-started/build-image.html.md @@ -164,10 +164,10 @@ want to try to launch your AMI, get the ID from the Packer output. -> **Note:** If you see a `VPCResourceNotSpecified` error, Packer might not be able to determine the default VPC, which the `t2` instance types require. This -can happen if you created you AWS account before `2013-12-04`. You can either +can happen if you created your AWS account before `2013-12-04`. You can either change the `instance_type` to `m3.medium`, or specify a VPC. Please see http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/default-vpc.html for more -information. +information. Specify a `vpc_id` and you will need to specify a `subnet_id`. ## Managing the Image