AWS AmazonElastiCache documentation change
Summary
Updated versioning terminology to use uppercase (MAJOR/MINOR/PATCH) and removed bold formatting from version examples
Security assessment
Changes are stylistic (capitalization/formatting adjustments) to align with semantic versioning conventions. No explicit security vulnerabilities, fixes, or new security features are mentioned. The existing reference to 'enhanced security' in automatic patch management remains unchanged.
Diff
diff --git a/AmazonElastiCache/latest/dg/VersionManagementConsiderations.md b/AmazonElastiCache/latest/dg/VersionManagementConsiderations.md index 8796a7f6e..b41df01a6 100644 --- a/AmazonElastiCache/latest/dg/VersionManagementConsiderations.md +++ b/AmazonElastiCache/latest/dg/VersionManagementConsiderations.md @@ -15 +15 @@ You can upgrade directly from your current Redis OSS version to the latest Redis -Redis OSS versions are identified with a semantic version which comprise a major, minor, and patch component. For example, in Redis OSS 4.0.10, the major version is 4, the minor version 0, and the patch version is 10. These values are generally incremented based off the following conventions: +Redis OSS versions are identified with a semantic version which comprise a MAJOR, MINOR, and PATCH component. For example, in Redis OSS 4.0.10, the major version is 4, the minor version 0, and the patch version is 10. These values are generally incremented based off the following conventions: @@ -17 +17 @@ Redis OSS versions are identified with a semantic version which comprise a major - * Major versions are for API incompatible changes + * MAJOR versions are for API incompatible changes @@ -19 +19 @@ Redis OSS versions are identified with a semantic version which comprise a major - * Minor versions are for new functionality added in a backwards-compatible way + * MINOR versions are for new functionality added in a backwards-compatible way @@ -21 +21 @@ Redis OSS versions are identified with a semantic version which comprise a major - * Patch versions are for backwards-compatible bug fixes and non-functional changes + * PATCH versions are for backwards-compatible bug fixes and non-functional changes @@ -26 +26 @@ Redis OSS versions are identified with a semantic version which comprise a major -We recommend always staying on the latest patch version within a given **major.minor** version in order to have the latest performance and stability improvements. Beginning with ElastiCache version 6.0 for Redis OSS, ElastiCache will offer a single version for each Redis OSS minor release rather than offering multiple patch versions. ElastiCache will automatically manage the patch version of your running cache clusters, ensuring improved performance and enhanced security. +We recommend always staying on the latest patch version within a given MAJOR.MINOR version in order to have the latest performance and stability improvements. Beginning with ElastiCache version 6.0 for Redis OSS, ElastiCache will offer a single version for each Redis OSS minor release rather than offering multiple patch versions. ElastiCache will automatically manage the patch version of your running cache clusters, ensuring improved performance and enhanced security. @@ -28 +28 @@ We recommend always staying on the latest patch version within a given **major.m -We also recommend periodically upgrading to the latest major version, since most major improvements are not back ported to older versions. As ElastiCache expands availability to a new AWS region, ElastiCache for Redis OSS supports the two most recent **major.minor** versions at that time for the new region. For example, if a new AWS region launches and the latest major.minor ElastiCache versions for Redis OSS are **7.0** and **6.2** , ElastiCache will support Redis OSS versions **7.0** and **6.2** in the new AWS region. As newer major.minor versions of ElastiCache for Redis OSS are released, ElastiCache will continue to add support for the newly released versions. To learn more about choosing regions for ElastiCache, see [Choosing regions and availability zones](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/RegionsAndAZs.html#SupportedRegions). +We also recommend periodically upgrading to the latest major version, since most major improvements are not back ported to older versions. As ElastiCache expands availability to a new AWS region, ElastiCache for Redis OSS supports the two most recent MAJOR.MINOR versions at that time for the new region. For example, if a new AWS region launches and the latest MAJOR.MINOR ElastiCache versions for Redis OSS are 7.0 and 6.2, ElastiCache will support Redis OSS versions 7.0 and 6.2 in the new AWS region. As newer MAJOR.MINOR versions of ElastiCache for Redis OSS are released, ElastiCache will continue to add support for the newly released versions. To learn more about choosing regions for ElastiCache, see [Choosing regions and availability zones](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/RegionsAndAZs.html#SupportedRegions).