AWS Elastic Beanstalk
Developer Guide (API Version 2010-12-01)
AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.

Deploying a Git Branch to a Specific Environment

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).

Developers often use branching in a project to manage code intended for different target environments. For example, you might have a test branch where you perform component or integration testing and a prod branch where you manage the code for your live or production code. With version 2.3 and later of the eb command line interface and AWS DevTools, you can use the eb init command to configure the eb push command to push your current git branch to a specific Elastic Beanstalk environment.

To set up a Git branch to deploy to a specific environment

  1. Make sure you have version 2.3 of the Elastic Beanstalk command line tools installed.

    To check what version you have installed, use the following command:

    eb --version

    To download the command line tools, go to Elastic Beanstalk Command Line Tool page and follow the instructions in the README.txt file in the .zip file.

  2. From a command prompt, change directories to the location of the local repository containing the code you want to deploy.

    If you have not set up a Git repository, you need to create one to continue. For information about how to use Git, see the Git documentation.

  3. Make sure that the current branch for your local repository is the one you want to map to an Elastic Beanstalk environment.

    To switch to a branch, you use the git checkout command. For example, you would use the following command to switch to the prod branch.

    git checkout prod

    For more information about creating and managing branches in Git, see the Git documentation.

  4. If you have not done so already, use the eb init command to configure eb to use Elastic Beanstalk with a specific settings for credentials, application, region, environment, and solution stack. The values set with eb init will be used as defaults for the environments that you create for your branches. For detailed instructions, see Step 2: Configure Elastic Beanstalk.

  5. Use the eb branch command to map the current branch to a specific environment.

    1. Type the following command.

      eb branch
    2. When prompted for an environment name, enter the name of the environment that you want to map to the current branch.

      The eb command will suggest a name in parentheses and you can accept that name by pressing the Enter key or type the name that you want.

      The current branch is "myotherbranch".
          Enter an Elastic Beanstalk environment name (auto-generated value is "test-myotherbranch-en"):

      You'll notice that eb displays the current branch in your Git repository so you know which branch you're working with. You can specify an existing environment or a new one. If you specify a new one, you'll need to create it with the eb start command.

    3. When prompted about using the settings from the default environment, type y unless you explicitly don't want to use the optionsettings file from the default environment for the environment for this branch.

      Do you want to copy the settings from the default environment "main-env" for the new branch? [y/n]: y
  6. If you specified a new environment for your branch, use the eb start command to create and start the environment.

    When this command is successful, you're ready for the next step.

  7. Use the eb push command to deploy the changes in the current branch to the environment that you mapped to the branch.