Managing application versions
This topic explains application versions and how to create and manage them.
Elastic Beanstalk creates an application version whenever you upload source code. This usually occurs when you create an environment or upload and deploy code using the environment management console or EB CLI. Elastic Beanstalk deletes these application versions according to the application's lifecycle policy and when you delete the application. For details about application lifecycle policy, see Configuring application version lifecycle settings.
You can also upload a source bundle without deploying it from the application management console or with the EB CLI command eb appversion. Elastic Beanstalk stores source bundles in Amazon Simple Storage Service (Amazon S3) and doesn't automatically delete them.
You can apply tags to an application version when you create it, and edit tags of existing application versions. For details, see Tagging application versions.
Creating application versions
You can also create a new application version using the EB CLI. For more information, see eb appversion in the EB CLI commands chapter.
Note
Over time, your application can accumulate many application versions. To save storage space and avoid hitting the application version quota, it's a good idea to delete application versions that you no longer need.
The file you specify in the following procedure is associated with your application. You can deploy the application version to a new or existing environment.
To create a new application version
Open the Elastic Beanstalk console
, and in the Regions list, select your AWS Region. -
In the navigation pane, choose Applications, and then choose your application's name from the list.
Note
If you have many applications, use the search bar to filter the application list.
In the navigation pane, find your application's name and choose Application versions.
-
Choose Upload. Use the on-screen form to upload your application's source bundle.
Note
The source bundle's file size limit is 500 MB.
-
Optionally, provide a brief description, and add tag keys and values.
-
Choose Upload.
Deleting application versions
You can also delete an application version using the EB CLI. For more information, see eb appversion in the EB CLI commands chapter.
Note
Deleting an application version doesn't affect environments currently running that version.
You can also configure Elastic Beanstalk to delete old versions automatically by configuring application version lifecycle settings. If you configure these lifecycle settings, they're applied when you create new application versions. For example, if you configure a maximum of 25 application versions, Elastic Beanstalk deletes the oldest version when you upload a 26th version. If you set a maximum age of 90 days, any versions older than 90 days are deleted when you upload a new version. For details, see Configuring application version lifecycle settings.
To delete an application version
Open the Elastic Beanstalk console
, and in the Regions list, select your AWS Region. -
In the navigation pane, choose Applications, and then choose your application's name from the list.
Note
If you have many applications, use the search bar to filter the application list.
In the navigation pane, find your application's name and choose Application versions.
-
Select one or more application versions that you want to delete.
-
Choose Actions, then choose Delete.
-
(Optional) To leave the application source bundle for these application versions in your Amazon Simple Storage Service (Amazon S3) bucket, clear the box for Delete versions from Amazon S3.
-
Choose Delete.
If you don't choose to delete the source bundle from Amazon S3, Elastic Beanstalk still deletes the version from its records. However, the source bundle is left in your Elastic Beanstalk storage bucket. The application version quota applies only to versions Elastic Beanstalk tracks. Therefore, you can delete versions to stay within the quota, but retain all source bundles in Amazon S3.
Note
The application version quota doesn't apply to source bundles, but you might still incur Amazon S3 charges, and retain personal information beyond the time you need it. Elastic Beanstalk never deletes source bundles automatically. You should delete source bundles when you no longer need them.
