Elastic beanstalk deployment taking longer than timeout period, how do I increase timeout period

Question

Elastic beanstalk deployment of a new environment for an application using the AWS website warns

Create environment operation is complete, but with command t         


        

Answer 1

You can do this using option settings. Option settings can be specified using ebextensions.

Create a file in your app source in a directory called .ebextensions. Lets say the file is .ebextensions/01-increase-timeout.config.

The contents of the file should be:

option_settings:
    - namespace: aws:elasticbeanstalk:command
      option_name: Timeout
      value: 1000

Note this file is in YAML format. After this you can update your environment with this version of source code.

From documentation for this option setting:

Timeout: Number of seconds to wait for an instance to complete executing commands.

For example, if source code deployment tasks are still running when you reach the configured timeout period, AWS Elastic Beanstalk displays the following error: "Some instances have not responded to commands. Responses were not received from ." You can increase the amount of time that the AWS Elastic Beanstalk service waits for your source code to successfully deploy to the instance.

You can read more about ebextensions here. Documentation on option settings is available here.

Answer 2

According to the official documentation you can pass --timeout option to your eb create call.

--timeout minutes
Set number of minutes before the command times out.

Answer 3

I've just been doing it at time of deployment for my environment and it works fine this way too.

eb deploy production-env --timeout 30

..and that gives me 30 minutes.

Answer 4

Use: --timeout

For eg: eb create -db --timeout 20

This will give you 20 minutes of timeout limit.