c4.large requires a VPC

[watchwithmike]

Using the latest code from master and following the README.md, I get the following error due to c4.large requiring a VPC.

ERROR: Creating Auto Scaling group named: awseb-e-XXXXXXXXX-stack-AWSEBAutoScalingGroup-LPMU6SAD3K5W failed. Reason: 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. Launching EC2 instance failed.

Changing the command to a c3.large succeeds, e.g.:

eb create -i c3.large --scale 1 --envvars TARGET_URL=<test URL> --instance_profile aws-elasticbeanstalk-locust-role

[abhiksingh]

Thanks for pointing out the VPC requirement @watchwithmike. For most folks who created their AWS accounts in 2014 or later, this should work as is due to the default VPC. I will look into updating the instructions for those deploying to a manually created VPC.

[shaikshakeel]

Hi,
any update on this ?

[abhiksingh]

@shaikshakeel what are you looking for? Instructions on running the app in a VPC using C4 instances?

[shaikshakeel]

@abhiksingh while creating Elastic Beanstalk using eb create .... command it is using default VPC as u said.

Is there any update on this ? using our own VPC ?

[vipinkumar1234]

Hi @abhiksingh while running eb create i am getting error = Instance deployment failed. For details, see 'eb-engine.log'
and i checked eb-engine-log and there is issue like Attempting to install ['locustio==0.8.1', 'pyzmq==16.0.3'] via easy_install
[ERROR] easy_install failed. Output: Searching for locustio==0.8.1

any idea how to resolve this i already tried with instance type c4.large, c4.xlarge and making change in setup.confiig locustio: [ "0.8.1" ] to locust: [ "0.8.1" ] because locust move from locustio to locust..