Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Elastic beanstalk fails to create

I am trying to run beanstalk with java installed on it very quickly.

So what I do is just open the beanstalk console and after creating the application I create the environment and in the environment pre configuration I chose java.

Then after clicking the create button I get some errors:

Creating security group named: awseb-e-rnwzmmymhx-stack-AWSEBSecurityGroup-SXHGXGDOF5PN failed Reason: Resource creation cancelled

Stack named 'awseb-e-rnwzmmymhx-stack' aborted operation. Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: [AWSEBEIP, AWSEBSecurityGroup].

Or the more complete error stack is as follow: enter image description here

I never attached any EIP and I just let beanstalk handle it . What is the problem?

Should I configure anything else? (Any idea is appreciated.)

Or better to ask this way: Do we need to attach EIP to beanstalk to have it work or there is a workatound using rout53?

like image 637
Hamed Minaee Avatar asked Jun 23 '17 14:06

Hamed Minaee


People also ask

What does Elastic Beanstalk create?

Elastic Beanstalk is a platform within AWS that is used for deploying and scaling web applications. In simple terms this platform as a service (PaaS) takes your application code and deploys it while provisioning the supporting architecture and compute resources required for your code to run.

When should you not use Elastic Beanstalk?

Elastic Beanstalk isn't great if you need a lot of environment variables. The simple reason is that Elastic Beanstalk has a hard limit of 4KB to store all key-value pairs. The environment had accumulated 74 environment variables — a few of them had exceedingly verbose names.

What happens if a rolling update fails in AWS Elastic Beanstalk?

If the rolling update process fails, Elastic Beanstalk starts another rolling update to roll back to the previous configuration. A rolling update can fail due to failed health checks or if launching new instances causes you to exceed the quotas on your account.


1 Answers

Each account has a maximum EIP limit (default is 5). Elastic BeanStalk is not able to get an EIP allocated since your account already used the maximum number of EIPs. You have at least two options:

  • Release unused EIP (making sure it is not used)
  • Raise a support request to increase the EIP limit. Usually it is fulfilled within hours

AWS Elastic IP Address Limit

like image 146
helloV Avatar answered Oct 04 '22 11:10

helloV