Creating an Elastic Beanstalk environment - AWS Elastic Beanstalk

Creating an Elastic Beanstalk environment

An AWS Elastic Beanstalk environment is a collection of AWS resources running an application version. You can deploy multiple environments when you need to run multiple versions of an application. For example, you might have development, integration, and production environments.

The following procedure launches a new environment running the default application. These steps are simplified to get your environment up and running quickly, using default option values. For detailed instructions with descriptions of the many options you can use to configure the resources that Elastic Beanstalk deploys on your behalf, see The create new environment wizard.

Notes
Old console
To launch an environment with a sample application (console)
  1. Open the Elastic Beanstalk console, and in the Regions list, select your AWS Region.

  2. In the navigation pane, choose Applications, and then choose an existing application's name in the list or create one.

  3. On the application overview page, choose Create a new environment.

    
              The application overview page with a list of application environments on the Elastic Beanstalk console
  4. Next, for environment tier, choose the Web server environment or Worker environment environment tier. You can't change an environment's tier after creation.

    Note

    The .NET on Windows Server platform doesn't support the worker environment tier.

    
              The Select environment tier page on the Elastic Beanstalk console
  5. For Platform, select the platform and platform branch that match the language your application uses.

    Note

    Elastic Beanstalk supports multiple versions for most of the platforms that are listed. By default, the console selects the recommended version for the platform and platform branch you choose. If your application requires a different version, you can select it here, or choose Configure more options, as described in step 7. For information about supported platform versions, see Elastic Beanstalk supported platforms.

  6. For Application code, choose Sample application.

  7. To further customize your environment, choose Configure more options. You can set the following options only during environment creation:

    • Environment name

    • Domain name

    • Platform version

    • Processor

    • VPC

    • Tier

    You can change the following settings after environment creation, but they require new instances or other resources to be provisioned and can take a long time to apply:

    • Instance type, root volume, key pair, and AWS Identity and Access Management (IAM) role

    • Internal Amazon RDS database

    • Load balancer

    For details on all available settings, see The create new environment wizard.

  8. Choose Create environment.

New console
Note

We're releasing a new Elastic Beanstalk console experience. The new console design is being released in a phased rollout to all regions that Elastic Beanstalk supports. It’s presently available in the following AWS Regions:

  • Beta release in US East (N. Virginia)— us-east-1

  • Asia Pacific (Sydney) — ap-southeast-2

  • Europe (Frankfurt) — eu-central-1

  • Europe (Ireland) — eu-west-1

  • South America (São Paulo) — sa-east-1

For more information, see the March 22, 2023 Release Notes in the AWS Elastic Beanstalk Release Notes guide.

To launch an environment with a sample application (console)
  1. Open the Elastic Beanstalk console, and in the Regions list, select your AWS Region.

  2. In the navigation pane, choose Applications, and then choose an existing application's name in the list or create one.

  3. On the application overview page, choose Create new environment.

    
              The application overview page with a list of application environments on the Elastic Beanstalk console

    This launches the Create environment wizard. The wizard provides a set of steps for you to create a new environment.

    
              The Create environment wizard on the Elastic Beanstalk console
  4. For environment tier, choose the Web server environment or Worker environment environment tier. You can't change an environment's tier after creation.

    Note

    The .NET on Windows Server platform doesn't support the worker environment tier.

  5. For Platform, select the platform and platform branch that match the language your application uses.

    Note

    Elastic Beanstalk supports multiple versions for most of the platforms that are listed. By default, the console selects the recommended version for the platform and platform branch you choose. If your application requires a different version, you can select it here. For information about supported platform versions, see Elastic Beanstalk supported platforms.

  6. For Application code, choose Sample application.

  7. For Configuration presets, choose Single instance.

  8. Choose Next.

  9. Choose Skip to Review on the Configure service access page.

    This will select the default values for this step and skip the optional steps.

  10. The Review page displays a summary of all your choices.

    To further customize your environment, choose Edit next to the step that includes any items you want to configure. You can set the following options only during environment creation:

    • Environment name

    • Domain name

    • Platform version

    • Processor

    • VPC

    • Tier

    You can change the following settings after environment creation, but they require new instances or other resources to be provisioned and can take a long time to apply:

    • Instance type, root volume, key pair, and AWS Identity and Access Management (IAM) role

    • Internal Amazon RDS database

    • Load balancer

    For details on all available settings, see The create new environment wizard.

  11. Choose Submit at the bottom of the page to initialize the creation of your new environment.

While Elastic Beanstalk creates your environment, you are redirected to the Elastic Beanstalk console. When the environment health turns green, choose the URL next to the environment name to view the running application. This URL is generally accessible from the internet unless you configure your environment to use a custom VPC with an internal load balancer.