Cant launch new EB ruby env - failing on AWSEBInstanceLaunchWaitCondition

Hello,

I'm attempting to spin up a new application environment in Elastic Beanstalk with a Ruby 2.6 and Passenger build. But I can't get past a AWSEBInstanceLaunchWaitCondition failure on every attempt.

I cannot edit configs after the failed launch because the app is never in "Ready" state, so I'm stuck just rebuilding over and over again.

If this is an issue with my default VPC, Security Groups, or whatever, how can I tell beanstalk to create a new VPC and security group with the correct configurations?

I've tried the following options through the console:

• selecting both a Ruby and a Node build just to see if Ruby platform was the problem
• Deploy Sample Application
• Deploy my new app
• Deploy an app that's successfully on running on Beanstalk on my other account
• Free Tier Eligible option
• High Availability option
• Custom config
• longer timeout
• do not fail on health check failure
• more instances in auto scaling group

I've tried via the console and the CLI. Same AWSEBInstanceLaunchWaitCondition error launching a new environment from the CLI. I'm probably racking up charges due to all thee failed deployments so reaching out for some help at this point. I haven't had this issue with beanstalk before. Current failed env id is e-ryvsuzzkjr though I have created and deleted at least 10 others over the last few days.

Thanks!

Edited by: harrisjb on Apr 30, 2019 1:18 AM