AWS elasticbeanstalk documentation change
Summary
Updated platform version and branch lifecycle terminology, added CLI verification methods, clarified EOL component handling, and improved update recommendations
Security assessment
Changes focus on lifecycle management and update recommendations rather than addressing specific vulnerabilities. While encouraging updates improves security posture generally, there's no mention of patching vulnerabilities or mitigating active threats.
Diff
diff --git a/elasticbeanstalk/latest/dg/platforms-glossary.md b/elasticbeanstalk/latest/dg/platforms-glossary.md index 74c124964..bccf73baf 100644 --- a//elasticbeanstalk/latest/dg/platforms-glossary.md +++ b//elasticbeanstalk/latest/dg/platforms-glossary.md @@ -33 +33 @@ A platform version can be in one of the following states: - * _Supported_ – A platform version that consists entirely of _supported components_. All components have not reached their End of Life (EOL), as designated by their respective suppliers (owners—AWS or third parties—or communities). They receive regular patch or minor updates from their suppliers . Elastic Beanstalk makes supported platform versions available to you for environment creation. + * _Recommended_ – The latest platform version in a supported platform branch. This version contains the most up-to-date components and is recommended for use in production environments. @@ -35 +35 @@ A platform version can be in one of the following states: - * _Retired_ – A platform version with one or more _retired components_ , which have reached their End of Life (EOL), as designated by their suppliers. Retired platform versions aren't available for use in Elastic Beanstalk environments for either new or existing customers. + * _Not Recommended_ – Any platform version that is not the latest version in its platform branch. While these versions may remain functional, we strongly recommend updating to the latest platform version. You can use [managed platform updates](./environment-platform-update-managed.html) to help stay up-to-date automatically. @@ -37 +36,0 @@ A platform version can be in one of the following states: -For details about retired components, see [Elastic Beanstalk platform support policy](./platforms-support-policy.html). @@ -40,0 +40 @@ For details about retired components, see [Elastic Beanstalk platform support po +You can verify if a platform version is recommended using the AWS CLI command **[describe-platform-version](https://docs.aws.amazon.com/cli/latest/reference/elasticbeanstalk/describe-platform-version.html)** and checking the `PlatformLifecycleState` field. @@ -45 +45 @@ For details about retired components, see [Elastic Beanstalk platform support po -A line of platform versions sharing specific (typically major) versions of some of their components, such as the operating system (OS), runtime, or Elastic Beanstalk components. For example: _Python 3.6 running on 64bit Amazon Linux_ ; _IIS 10.0 running on 64bit Windows Server 2016_. Each successive platform version in the branch is an update to the previous one. +A line of platform versions sharing specific (typically major) versions of some of their components, such as the operating system (OS), runtime, or Elastic Beanstalk components. For example: _Python 3.13 running on 64bit Amazon Linux 2023_ ; _IIS 10.0 running on 64bit Windows Server 2025_. Platform branches receive updates in the form of new platform versions. Each successive platform version in a branch is an update to the previous one. @@ -47 +47 @@ A line of platform versions sharing specific (typically major) versions of some -The latest platform version in each platform branch is available to you unconditionally for environment creation. Previous platform versions in the branch are still supported—you can create an environment based on a previous platform version if you've used it in an environment in the last 30 days. But these previous platform versions lack the most up-to-date components and aren't recommended for use. +The recommended version in each supported platform branch is available to you unconditionally for environment creation. A previous platform version is available to you if you were using an environment with it at the time the platform version was superceded by a new platform version. Previous platform versions lack the most up-to-date components and aren't recommended for use. @@ -51 +51 @@ A platform branch can be in one of the following states: - * _Supported_ – A current platform branch. It consists entirely of _supported components_. It receives ongoing platform updates, and is recommended for use in production environments. For a list of supported platform branches, see [Elastic Beanstalk supported platforms](https://docs.aws.amazon.com/elasticbeanstalk/latest/platforms/platforms-supported.html) in the _AWS Elastic Beanstalk Platforms_ guide. + * _Supported_ – A current platform branch. It consists entirely of _supported components_. Supported components have not reached End of Life (EOL), as designated by their suppliers. It receives ongoing platform updates, and is recommended for use in production environments. For a list of supported platform branches, see [Elastic Beanstalk supported platforms](https://docs.aws.amazon.com/elasticbeanstalk/latest/platforms/platforms-supported.html) in the _AWS Elastic Beanstalk Platforms_ guide. @@ -55 +55 @@ A platform branch can be in one of the following states: - * _Deprecated_ – A platform branch with one or more _deprecated components_. It receives ongoing platform updates, but isn't recommended for use in production environments. For a list of deprecated platform branches, see [Elastic Beanstalk Platform Versions Scheduled for Retirement](https://docs.aws.amazon.com/elasticbeanstalk/latest/platforms/platforms-retiring.html) in the _AWS Elastic Beanstalk Platforms_ guide. + * _Deprecated_ – A platform branch where one or more components (such as the runtime or operating system) are approaching End of Life (EOL) or have reached EOL, as designated by their suppliers. While a deprecated platform branch continues to receive new platform versions until its retirement date, components that have reached EOL don't receive updates. For example, if a runtime version reaches EOL, the platform branch will be marked as deprecated but will continue to receive operating system updates until the platform branch retirement date. The platform branch will not continue to receive updates to the EOL runtime version. A deprecated platform branch isn't recommended for use. @@ -57 +57 @@ A platform branch can be in one of the following states: - * _Retired_ – A platform branch with one or more _retired components_. It doesn't receive platform updates anymore, and isn't recommended for use in production environments. Retired platform branches aren't listed in the _AWS Elastic Beanstalk Platforms_ guide. Elastic Beanstalk doesn't make platform versions of retired platform branches available to you for environment creation. + * _Retired_ – A platform branch that no longer receives any updates. Retired platform branches aren't available to create new Elastic Beanstalk environments using the Elastic Beanstalk console. If your environment uses a retired platform branch, you must update to a supported platform branch to continue receiving updates. A retired platform branch isn't recommended for use. For more details about retired platform branches, see [Elastic Beanstalk platform support policy](./platforms-support-policy.html). For a list of platform branches scheduled for retirement, see [Retiring platform branch schedule](https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/platforms-schedule.html#platforms-support-policy.depracation). To see past retired platform branches, see [Retired platform branch history](https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/platforms-schedule.html#platforms-support-policy.retired). @@ -62,2 +61,0 @@ A platform branch can be in one of the following states: -A _supported component_ has no retirement date scheduled by its supplier (owner or community). The supplier might be AWS or a third party. A _deprecated component_ has a retirement date scheduled by its supplier. A _retired component_ has reached End of Life (EOL) and is no longer supported by its supplier. For details about retired components, see [Elastic Beanstalk platform support policy](./platforms-support-policy.html). - @@ -65,0 +64,2 @@ If your environment uses a deprecated or retired platform branch, we recommend t +You can verify the state of a platform branch using the AWS CLI command **[describe-platform-version](https://docs.aws.amazon.com/cli/latest/reference/elasticbeanstalk/describe-platform-version.html)** and checking the `PlatformBranchLifecycleState` field. + @@ -69 +69 @@ If your environment uses a deprecated or retired platform branch, we recommend t -A release of new platform versions that contain updates to some components of the platform—OS, runtime, web server, application server, and Elastic Beanstalk components. Platform updates follow semantic version taxonomy, and can have several levels: +A release of new platform versions that contain updates to some components of the platform—OS, runtime, web server, application server, and Elastic Beanstalk components. Platform updates follow semantic version taxonomy, and can have three levels: @@ -71 +71 @@ A release of new platform versions that contain updates to some components of th - * _Major update_ – An update that has changes that are incompatible with existing platform versions. You might need to modify your application to run correctly on a new major version. A major update has a new major platform version number. + * _Major update_ – An update that has changes that are incompatible with existing platform versions. You may need to modify your application to run correctly on a new major version. A major update has a new major platform version number. @@ -73 +73 @@ A release of new platform versions that contain updates to some components of th - * _Minor update_ – An update that adds functionality that is backward compatible with an existing platform version. You don't need to modify your application to run correctly on a new minor version. A minor update has a new minor platform version number. + * _Minor update_ – An update that has changes that are backward compatible with existing platform versions in most cases. Depending on your application, you may need to modify your application to run correctly on a new minor version. A minor update has a new minor platform version number.