AWS Elastic Beanstalk
Developer Guide

The AWS Documentation website is getting a new look!
Try it now and let us know what you think. Switch to the new look >>

You can return to the original look by selecting English in the language selector above.

Migrating Your Application from a Legacy Container Type

If you have deployed an Elastic Beanstalk application that uses a legacy container type, you should migrate your application to a new environment using a non-legacy container type so that you can get access to new features. If you are unsure whether you are running your application using a legacy container type, you can check in the Elastic Beanstalk console. For instructions, see To check if you are using a legacy container type.

What new features are legacy containers missing?

Legacy platforms do not support the following features:

Why are some container types marked legacy?

Some older platform versions do not support the latest Elastic Beanstalk features. These versions are marked (legacy) on the environment configuration page in the AWS Management Console.

To check if you are using a legacy container type

  1. Open the Elastic Beanstalk console.

  2. From the Elastic Beanstalk console applications page, click the environment that you want to verify.

  3. In the Overview section of the environment dashboard, view the Configuration name.

    Your application is using a legacy container type if you see (legacy) next to the configuration.

To migrate your application

  1. Deploy your application to a new environment. For instructions, go to Creating an AWS Elastic Beanstalk Environment.

  2. If you have an Amazon RDS DB Instance, update your database security group to allow access to your EC2 security group for your new environment. For instructions on how to find the name of your EC2 security group using the AWS Management Console, see Security Groups. For more information about configuring your EC2 security group, go to the "Authorizing Network Access to an Amazon EC2 Security Group" section of Working with DB Security Groups in the Amazon Relational Database Service User Guide.

  3. Swap your environment URL. For instructions, go to Blue/Green Deployments with Elastic Beanstalk.

  4. Terminate your old environment. For instructions, go to Terminate an Elastic Beanstalk Environment.


If you use AWS Identity and Access Management (IAM) then you will need to update your policies to include AWS CloudFormation and Amazon RDS (if applicable). For more information, see Using Elastic Beanstalk with AWS Identity and Access Management.