brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [42/50] brooklyn-docs git commit: Describes AWS VPC issue
Date Mon, 01 Feb 2016 17:44:57 GMT
Describes AWS VPC issue


Branch: refs/heads/0.7.0-incubating
Commit: 0c88c44423ad5a52a349ed8668bf245325022fdb
Parents: 267e59d
Author: Duncan Grant <>
Authored: Tue Jun 23 14:31:33 2015 +0100
Committer: Duncan Grant <>
Committed: Tue Jun 23 14:31:33 2015 +0100

 docs/guide/ops/locations/ | 38 ++++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)
diff --git a/docs/guide/ops/locations/ b/docs/guide/ops/locations/
index 78f185d..e6c7035 100644
--- a/docs/guide/ops/locations/
+++ b/docs/guide/ops/locations/
@@ -210,6 +210,44 @@ For more keys and more detail on the keys below, see
   This setting prevents scripts executed on the VMs from being deleted on completion.
   Note that some scripts run periodically so this can eventually fill a disk; it should only
be used for dev/test. 
+### AWS VPC issues which may affect users with older AWS accounts
+AWS now has different default behaviour depending on the age of your AWS account and whether
you used the target region before, or during, 2013.
+In this case VM provisioning may fail with an error like:
+{% highlight text %}
+Detected that your EC2 account is a legacy 'classic' account, but the recommended instance
type requires VPC. 
+You can specify the 'eu-central-1' region to avoid this problem, or you can specify a classic-compatible
instance type, 
+or you can specify a subnet to use with 'networkName' 
+taking care that the subnet auto-assigns public IP's and allows ingress on all ports, 
+as Brooklyn does not currently configure security groups for non-default VPC's; 
+or setting up Brooklyn to be in the subnet or have a jump host or other subnet access configuration).

+For more information on VPC vs classic see
+{% endhighlight %}
+Specifically, there are issues with the certain AMIs and instance types.  If these are specified
or a recommended 
+by brooklyn then you may see the above error. There are a few options for fixing this:
+- specify a different region which does not support EC2-classic.  
+  You can check this on the AWS console under "Supported Platforms.
+  Frankfurt (eu-central-1) is guaranteed to be VPC only.
+- specify an instance type that is compatible with ec2-classic.  
+  Instance types C4, M4, T2 are only supported in VPC so should not be used.
+  This is described [here](index.html#vm-creation)
+- create a subnet to use with the instance. Ensure that the subnet is set to auto-assign
public IPs
+  and allows ingress on all ports.  Brooklyn cannot currently do this for you.
+  Use the networkName parameter to specify this value in your blueprint.
+See the following resources for more information:
+- [Amazon EC2 and Amazon Virtual Private Cloud](
+- [Your Default VPC and Subnets](
+- [Amazon VPC FAQs](
 ### Inheritance and Named Locations

View raw message