AWS Elastic Beanstalk
Release Notes

Release: EB CLI 3.14.7 on December 5, 2018

The AWS Elastic Beanstalk Command Line Interface (EB CLI) has a new version with bug fixes and new functionality.

Release date: December 5, 2018

Changes

Here is a list of the key changes in this release.

Change Affected commands Description

Application Load Balancer by default

eb create

When you create a load-balanced environment by using eb create and don't specify the --single option, the EB CLI now creates an Application Load Balancer by default. Previously, the default was a Classic Load Balancer.

In the interactive flow, the EB CLI now shows application (option 2) as the default load balancer type. In the non-interactive flow, the EB CLI defaults to Application Load Balancer unless you explicitly select a type by specifying the --elb-type option. For more information, see eb create in the AWS Elastic Beanstalk Developer Guide.

Important

If you have scripts that use the EB CLI to create an environment, the environment's source bundle might include configuration files that assume a Classic Load Balancer. To keep using a Classic Load Balancer, be sure to add --elb-type classic to the eb create command.

Private IP address for SSH

eb ssh

When a public IP address for your instance isn't found, the eb ssh command now uses a private IP address to connect to the instance. Previously, a private DNS name was used in the same case. DNS resolution isn't always available (for example, when accessing instances in VPCs in multiple AWS Regions through a single VPN). Using a private IP address should succeed more reliably.

Various bug fixes

eb create

eb init

eb tags

Fixed several minor bugs that affected the correct behavior of some commands.

On this page: