Github user ahgittin commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/705#issuecomment-114334161
confirmed for me too, specifying `minRam: 2gb` in AWS results in:
```
2015-06-22 19:33:29,968 ERROR Failed to start VM for
aws-ec2:eu-west-1@NginxControllerImpl{id=m8aiWnk1}: request POST
https://ec2.eu-west-1.amazonaws.com/ HTTP/1.1 failed with code 400, error:
AWSError{requestId='4e534c1d-1884-4776-a3e6-5efd470c9c79', requestToken='null',
code='VPCResourceNotSpecified', message='The specified instance type can only
be used in a VPC. A subnet ID or network interface ID is required to carry out
the request.', context='{Response=, Errors=}'}
```
We hit issues like this when writing
https://github.com/jclouds/jclouds/pull/732 and temporary local Brooklyn
patch/copy https://github.com/apache/incubator-brooklyn/pull/610 -- these
focussed on fixing the issue with selecting incompatible images, so it's
possible we need more fixes from the former PR added to Brooklyn. Or possibly
AWS have made more restrictive which instance types can run outwith a VPC.
More anon.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
