AWS AmazonRDS high security documentation change
Summary
Restructured content about LTS version notifications and patching process. Added bullet points detailing upgrade process communication and emphasized security-related critical fixes.
Security assessment
Explicitly mentions security issues as a reason for notifications with short notice and security fixes as a driver for more frequent LTS patching. This indicates documentation of existing security-related processes rather than introducing new features.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/Aurora.VersionPolicy.Support.md index e4657eb46..0cb8a7707 100644 --- a/AmazonRDS/latest/AuroraUserGuide/Aurora.VersionPolicy.Support.md +++ b/AmazonRDS/latest/AuroraUserGuide/Aurora.VersionPolicy.Support.md @@ -13 +13 @@ If your Amazon Aurora DB has complex dependencies on specific database engine be -For each Aurora major version, certain minor versions are designated as long-term-support (LTS) versions, and made available for at least three years. That is, at least one minor version per major version is made available for longer than the typical 12 months. Typically, Aurora reminds you six months before the end of this period. Aurora communicates the detailed upgrade process, including the timing of certain milestones, the impact on your DB clusters, and recommended actions. Notifications with less than six months notice communicate critical matters, such as security issues, that necessitate quicker action. +For each Aurora major version, certain minor versions are designated as long-term-support (LTS) versions, and made available for at least three years. That is, at least one minor version per major version is made available for longer than the typical 12 months. Typically, Aurora reminds you six months before the end of this period. Aurora communicates the following about the upgrade process. @@ -15 +15,12 @@ For each Aurora major version, certain minor versions are designated as long-ter -LTS minor versions include only critical fixes (through patch versions). An LTS version doesn't include new features released after its introduction. Once a year, DB clusters running on an LTS minor version are patched to the latest patch version of the LTS release. Aurora patches your clusters so that you benefit from cumulative security and stability fixes. Aurora might patch an LTS minor version more frequently if there are critical fixes, such as for security, that need to be applied. + * The timing of certain milestones + + * The impact on your DB clusters + + * Recommended actions + + + + +Notifications with less than six months notice communicate critical matters, such as security issues, that necessitate quicker action. + +LTS minor versions include only critical fixes (through patch versions). An LTS version doesn't include new features released after its introduction. Once a year, DB clusters running on an LTS minor version are patched to the latest patch version of the LTS release. Aurora patches your clusters so that you benefit from cumulative security and stability fixes. If there are critical fixes, Aurora might patch an LTS minor version more frequently, such as for security, that need to be applied.