ERROR on installing Parse server on AWS Elastic Beanstalk

[candork]

I am following this tutorial (http://mobile.awsblog.com/post/TxCD57GZLM2JR/How-to-set-up-Parse-Server-on-AWS-using-AWS-Elastic-Beanstalk) to install parse example on bean stalk.

But getting this error during the launch process. Any idea whats going on?

2016-04-28 22:17:28 UTC-0400 INFO Launched environment: parseserver-2p4z3-env. However, there were issues during launch. See event log for details.

2016-04-28 22:17:25 UTC-0400 ERROR Stack named 'awseb-e-b2hkj7pugi-stack' aborted operation. Current state:'CREATE_FAILED' Reason: The following resource(s) failed to create:[AWSEBAutoScalingGroup].

2016-04-28 22:17:24 UTC-0400 ERROR Creating Auto Scaling group named: awseb-e-b2hkj7pugi-stack-AWSEBAutoScalingGroup-1414ZZE9B4G64 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.

[dmennis]

@candork

We just had some reason inquiries about this and here's the solution and why this is happening. If you still have issues, please reach out to us in the Elastic Beanstalk forum.

Solution: Use this link here http://amzn.to/1YWsozK to deploy Parse Server onto Elastic Beanstalk. The only difference (from the "Deploy to AWS" button link in the blog) is the link specifies an EC2 instance type of m3.medium vs t2.small.

Issue: There are two AWS accounts, one has VPC by default and the other does not. Those accounts created after Dec 4, 2013 have default VPC (EC2-VPC) and all others do not (EC2-Classic). In our solution for Parse Server, the smallest (and free-tier) instance type is t2.micro which works for both account types, however, this instance type does not have enough memory to handle Parse Server. So, the next smallest instance type that works is a t2.small, however, t2.small is only available to EC2-VPC accounts. The next smallest size for EC2-Classic accounts is the m3.medium to run Parse Server on Elastic Beanstalk. Based on the number of launches, a large majority of the accounts launching this solution are EC2-VPC so we errored on the majority and didn't want to confuse users by offering multiple links and launching an m3.medium by default. If, for some reason, your account is EC2-VPC, it's possible the default VPC configuration was disabled, or misconfigured. If that's the case, m3.medium will still work for you. If you continue to have issues, please reach out to us in the Elastic Beanstalk forum here.

-Dennis
AWS Mobile

[cleever]

#150 (comment)

[sprabs]

@candork Did you ever get it working?

@dennisAWS We are also facing an issue with parse server on Elastic Beanstalk. I've tried contacting support without much luck. Do you have any ideas what can be happening: parse-community/parse-server#2061

[vladicabg]

I am getting the same error when I try to do a POST from the app after a series of GETs.
My app runs some verification on the startup and generates a series of GETs.

[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]

Next POST gives
*84 upstream prematurely closed connection while reading response header from upstream

I changed AWS setup to m3.medium as it was said here but no change