Menu
AWS Elastic Beanstalk
Developer Guide (API Version 2010-12-01)

Eb CLI 2.6 (deprecated)

Note

This version of the EB CLI and its documentation have been replaced with version 3. Version 3 has different commands and is not backwards compatible with version 2. For information on the new version, see The Elastic Beanstalk Command Line Interface (EB CLI).

This section describes how to set up eb 2.6 and how to create a sample application using eb. This section also includes a command reference for eb 2.6.

Differences from version 3 of the EB CLI

EB and Eb are command line interface (CLI) tools for Elastic Beanstalk that you can use to deploy applications quickly and more easily. The most recent tool that Elastic Beanstalk supports is EB CLI 3. Elastic Beanstalk also supports eb 2.6 for customers who previously installed and continue to use it. You can use EB CLI 3 to manage environments that you launched using eb 2.6 or earlier versions of eb. EB CLI will automatically retrieve settings from an environment created using eb if the environment is running. Unlike eb, EB CLI does not store option settings locally.

EB CLI introduces the commands eb create, eb deploy, eb open, eb console, eb scale, eb setenv, eb config, eb terminate, eb clone, eb list, eb use, eb printenv, and eb ssh. In EB CLI 3.1 or later, you can also use the eb swap command. In EB CLI 3.2 only, you can use the eb abort, eb platform, and eb upgrade commands. In addition to these new commands, EB CLI 3 commands differ from eb 2.6 commands in several cases:

  • eb init – You use eb init to create an .elasticbeanstalk directory in an existing project directory and create a new Elastic Beanstalk application for the project. Unlike with eb, running eb init with EB CLI does not prompt you to create an environment.

  • eb start – EB CLI does not include the command eb start. Instead, you use eb create to create an environment.

  • eb stop – EB CLI does not include the command eb stop. Instead, you use eb terminate to completely terminate an environment and clean up.

  • eb push and git aws.push – EB CLI does not include the commands eb push or git aws.push. The commands have been replaced with the command eb deploy.

  • eb update – EB CLI does not include the command eb update. You use the command eb config to update an environment.

  • eb branch – EB CLI does not include the command eb branch.

For more information about using EB CLI 3 commands to create and manage an application, go to EB CLI Command Reference. For a command reference for eb 2.6, see EB CLI 2 Commands. For a walkthrough of how to deploy a sample application using EB CLI 3, see Managing Elastic Beanstalk Environments with the EB CLI. For a walkthrough of how to deploy a sample application using eb 2.6, see Getting Started with Eb. For a walkthrough of how to use eb 2.6 to map a Git branch to a specific environment, see Deploying a Git Branch to a Specific Environment.