AWS health documentation change
Summary
Updated AWS Health event lifecycle details: changed event closure status formatting, extended event retention period from 90 days to 4 years, and rephrased security group responsibility wording.
Security assessment
The changes clarify operational processes (event status formatting, retention period extension) and rephrase existing security responsibility language without introducing new security content or addressing vulnerabilities. The retention period extension impacts data availability but isn't tied to a security vulnerability.
Diff
diff --git a/health/latest/ug/aws-health-planned-lifecycle-events.md b/health/latest/ug/aws-health-planned-lifecycle-events.md index 2c3871748..e69710ac4 100644 --- a//health/latest/ug/aws-health-planned-lifecycle-events.md +++ b//health/latest/ug/aws-health-planned-lifecycle-events.md @@ -92 +92 @@ Organizations can expect to receive a single event ARN for every planned lifecyc - 2. If you resolve all resources prior to the end of support date, then your AWS Health event changes to the status "Closed". + 2. If you resolve all resources prior to the end of support date, then your AWS Health event changes to the status `Closed`. @@ -94 +94 @@ Organizations can expect to receive a single event ARN for every planned lifecyc - 3. If you have outstanding resources after the date that aren't resolved, then the AWS Health event remains open for 90 days after the start or end date. Then the event is deleted. + 3. If you have outstanding resources after the change date that aren't resolved, then the AWS Health event remains open for 4 years after the event start or end date (whichever is later). After this time, the AWS Health event is deleted. @@ -101 +101 @@ Organizations can expect to receive a single event ARN for every planned lifecyc -Security and compliance are shared responsibilities between AWS and the customer. Depending on the services deployed, this shared model can help relieve the customer’s operational burden. This is because AWS operates, manages, and controls the components from the host operating system and virtualization layer down to the physical security of the facilities in which the service operates. The customer assumes responsibility and management of the guest operating system (including updates and security patches) and other associated application software, in addition to the configuration of the AWS-provided security group firewall. For more information, see [Shared responsibility model](https://docs.aws.amazon.com/whitepapers/latest/aws-risk-and-compliance/shared-responsibility-model.html). +Security and compliance are shared responsibilities between AWS and the customer. Depending on the services deployed, this shared model can help relieve the customer’s operational burden. This is because AWS operates, manages, and controls the components from the host operating system and virtualization layer down to the physical security of the facilities in which the service operates. The customer assumes responsibility and management of the guest operating system (including updates and security patches) and other associated application software, in addition to the configuration of the security group firewall provided by AWS. For more information, see [Shared responsibility model](https://docs.aws.amazon.com/whitepapers/latest/aws-risk-and-compliance/shared-responsibility-model.html).