AWS AmazonElastiCache documentation change
Summary
Capitalized semantic versioning terms (MAJOR/MINOR/PATCH) for consistency and emphasis in documentation
Security assessment
Changes only involve capitalization of version terminology without addressing vulnerabilities, security features, or incident responses
Diff
diff --git a/AmazonElastiCache/latest/dg/VersionManagement.md b/AmazonElastiCache/latest/dg/VersionManagement.md index 8205aa8c7..076a2266a 100644 --- a/AmazonElastiCache/latest/dg/VersionManagement.md +++ b/AmazonElastiCache/latest/dg/VersionManagement.md @@ -15 +15 @@ Manage if and when the ElastiCache Serverless cache is upgraded and perform vers -ElastiCache Serverless automatically applies the latest minor and patch software version to your cache, without any impact or downtime to your application. No action is required on your end. +ElastiCache Serverless automatically applies the latest MINOR and PATCH software version to your cache, without any impact or downtime to your application. No action is required on your end. @@ -17 +17 @@ ElastiCache Serverless automatically applies the latest minor and patch software -When a new major version is available, ElastiCache Serverless will send you a notification in the console and an event in EventBridge. You can choose to upgrade your cache to the latest major version by modifying your cache using the Console, CLI, or API and selecting the latest engine version. Similar to minor and patch upgrades, major version upgrades are performed without downtime to your application. +When a new MAJOR version is available, ElastiCache Serverless will send you a notification in the console and an event in EventBridge. You can choose to upgrade your cache to the latest major version by modifying your cache using the Console, CLI, or API and selecting the latest engine version. @@ -21 +21 @@ When a new major version is available, ElastiCache Serverless will send you a no -When working with self-designed ElastiCache clusters, you can control when the software powering your cache cluster is upgraded to new versions that are supported by ElastiCache. You can control when to upgrade your cache to the latest available major, minor, and patch versions. You initiate engine version upgrades to your cluster or replication group by modifying it and specifying a new engine version. +When working with self-designed ElastiCache clusters, you can control when the software powering your cache cluster is upgraded to new versions that are supported by ElastiCache. You can control when to upgrade your cache to the latest available MAJOR, MINOR, and PATCH versions. You initiate engine version upgrades to your cluster or replication group by modifying it and specifying a new engine version. @@ -33 +33 @@ Because version upgrades might involve some compatibility risk, they don't occur - * ElastiCache for Redis OSS versions are identified with a semantic version which comprise a major and minor component. For example, in Redis OSS 6.2, the major version is 6, and the minor version 2. When operating self-designed clusters, ElastiCache for Redis OSS also exposes the patch component, e.g. Redis OSS 6.2.1, and the patch version is 1. + * ElastiCache for Redis OSS versions are identified with a semantic version which comprise a MAJOR and MINOR component. For example, in Redis OSS 6.2, the major version is 6, and the minor version 2. When operating self-designed clusters, ElastiCache for Redis OSS also exposes the PATCH component, e.g. Redis OSS 6.2.1, and the patch version is 1. @@ -35 +35 @@ Because version upgrades might involve some compatibility risk, they don't occur -Major versions are for API incompatible changes and minor versions are for new functionality added in a backwards-compatible way. Patch versions are for backwards-compatible bug fixes and non-functional changes. +MAJOR versions are for API incompatible changes and MINOR versions are for new functionality added in a backwards-compatible way. PATCH versions are for backwards-compatible bug fixes and non-functional changes.