Can't create environment - Europe West

Question

Hi,  
  
Trying to launch an application, all default settings, Java platform, uploaded .zip file...  It just doesn't seem to be launching the instance or ever get any further than the log shown below...  
  
We tried launching in a different region - exact same steps - works without issue (developer's own account)  
  
The log below is for another try, default settings, but this time selecting the demo app...  It just seems to never get past the point of having to create the actual instances.  
  
2:46pm  
Launched environment: LLBokun-env. However, there were issues during launch. See event log for details.  
2:46pm  
Creating Auto Scaling group named:  
awseb-e-xe3r2rem3x-stack-AWSEBAutoScalingGroup-1C2M5G5VA3XCY failed. Reason: Group did not stabilize. {current/minSize/maxSize} group size = {0/1/1}. Failed Scaling Activity: No default subnet for availability zone: 'eu-central-1c'. Launching EC2 instance failed.  
2:46pm  
Stack named 'awseb-e-xe3r2rem3x-stack' aborted operation. Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: AWSEBAutoScalingGroup.  
2:00pm  
Environment health has transitioned from Pending to Severe. Initialization in progress (running for 15 minutes). There are no instances.  
1:45pm  
Environment health has transitioned to Pending. Initialization in progress (running for 11 seconds). There are no instances.  
1:45pm  
Created EIP: 52.28.99.167  
1:45pm  
Created security group named:  
awseb-e-xe3r2rem3x-stack-AWSEBSecurityGroup-L25C6RXHWIZL  
1:44pm  
Using elasticbeanstalk-eu-central-1-485314591840 as Amazon S3 storage bucket for environment data.  
1:44pm  
createEnvironment is starting.  
  
Help appreciated, thanks in advance!

Answer

Hello,  
  
As the error suggests, the environment failed to create mainly because the beanstalk was not able to find the default subnet in eu-central-1c. Usually such error occurs if you have not explicitly specified a custom VPC while creating the environment or if the default VPC has been deleted in the region.  
  
If we do not specify a custom VPC, beanstalk will by default, try to use the default VPC and subnets to launch the environment. Could you try recreating the default VPC and create a new EB environment:  
https://aws.amazon.com/premiumsupport/knowledge-center/deleted-default-vpc/

Answer

For anyone else stumbling upon this, the problem (as per log) was that no default VPC existed.  
  
How to create a new default VPC:  https://aws.amazon.com/premiumsupport/knowledge-center/deleted-default-vpc/  
  
In my case, I create a new VPC with subnets/routing/etc and did custom config and places environment inside that VPC

Can't create environment - Europe West

Relevant content