Migrating your application from a legacy platform version
If you have deployed an Elastic Beanstalk application that uses a legacy platform version, you should migrate your application to a new environment using a non-legacy platform version so that you can get access to new features. If you are unsure whether you are running your application using a legacy platform version, you can check in the Elastic Beanstalk console. For instructions, see To check if you are using a legacy platform version.
What new features are legacy platform versions missing?
Legacy platforms do not support the following features:
Configuration files, as described in the Advanced environment customization with configuration files (.ebextensions) topic
ELB health checks, as described in the Basic health reporting topic
Instance Profiles, as described in the Managing Elastic Beanstalk instance profiles topic
VPCs, as described in the Using Elastic Beanstalk with Amazon VPC topic
Data Tiers, as described in the Adding a database to your Elastic Beanstalk environment topic
Worker Tiers, as described in the Elastic Beanstalk worker environments topic
Single Instance Environments, as described in the Environment types topic
Tags, as described in the Tagging resources in your Elastic Beanstalk environments topic
Rolling Updates, as described in the Elastic Beanstalk rolling environment configuration updates topic
Why are some platform versions marked legacy?
Some older platform versions do not support the latest Elastic Beanstalk features. These versions are marked (legacy) on the environment overview page in the Elastic Beanstalk console.
To check if you are using a legacy platform version
Open the Elastic Beanstalk console
, and in the Regions list, select your AWS Region. -
In the navigation pane, choose Environments, and then choose the name of your environment from the list.
Note
If you have many environments, use the search bar to filter the environment list.
-
On the environment overview page, view the Platform name.
Your application is using a legacy platform version if you see (legacy) next to the platform's name.
To migrate your application
-
Deploy your application to a new environment. For instructions, go to Creating an Elastic Beanstalk environment.
-
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.
-
Swap your environment URL. For instructions, go to Blue/Green deployments with Elastic Beanstalk.
-
Terminate your old environment. For instructions, go to Terminate an Elastic Beanstalk environment.
Note
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.
