AWS AWSEC2: Clarified host maintenance automation wording
Summary
Changed active voice to passive voice in descriptions of host replacement and instance migration processes.
Security assessment
Changes are grammatical (active→passive voice) with no security implications, only clarifying operational processes.
Evidence
-When a degradation is detected on a Dedicated Host that is enabled for host maintenance, we automatically allocate a replacement Dedicated Host in your account. The replacement Dedicated Host receives a new host ID, but retains the same attributes as the original Dedicated Host, including:
Diff
diff --git a/AWSEC2/latest/UserGuide/dedicated-hosts-maintenance-basics.md b/AWSEC2/latest/UserGuide/dedicated-hosts-maintenance-basics.md index eef42b147..3fa00db5d 100644 --- a//AWSEC2/latest/UserGuide/dedicated-hosts-maintenance-basics.md +++ b//AWSEC2/latest/UserGuide/dedicated-hosts-maintenance-basics.md @@ -11 +11 @@ Live migration host maintenanceReboot-based host maintenanceHost maintenance sta -When a degradation is detected on a Dedicated Host that is enabled for host maintenance, we automatically allocate a replacement Dedicated Host in your account. The replacement Dedicated Host receives a new host ID, but retains the same attributes as the original Dedicated Host, including: +When a degradation is detected on a Dedicated Host that is enabled for host maintenance, a replacement Dedicated Host is automatically allocated in your account. The replacement Dedicated Host receives a new host ID, but retains the same attributes as the original Dedicated Host, including: @@ -32 +32 @@ When a degradation is detected on a Dedicated Host that is enabled for host main -After the replacement host has been allocated, we migrate the instances using either **live migration host maintenance** or **reboot-based host maintenance** , depending on the instance. +After the replacement host has been allocated, the instances are migrated using either **live migration host maintenance** or **reboot-based host maintenance** , depending on the instance. @@ -55 +55 @@ Some larger instance sizes might experience a slight performance decrease during -After the instances are automatically migrated to the replacement host, we send you email and AWS Health Dashboard notifications. Notifications include the IDs of the degraded and replacement hosts, information about the instances that were automatically migrated using live migration host maintenance, and information about the remaining instances. +After the instances are automatically migrated to the replacement host, you receive email and AWS Health Dashboard notifications. Notifications include the IDs of the degraded and replacement hosts, information about the instances that were automatically migrated using live migration host maintenance, and information about the remaining instances. @@ -100 +100 @@ Some instances can't be automatically migrated to the replacement host. -For these instances, we schedule instance stop events for 28 days from the date of the notification. At the date and time of the scheduled event, the instances are stopped. We recommend that you manually stop on restart the instance on the replacement host or on a different host. You might need to modify your instance's host affinity to restart it on a different host. +For these instances, instance stop events are scheduled for 28 days from the date of the notification. At the date and time of the scheduled event, the instances are stopped. We recommend that you manually stop on restart the instance on the replacement host or on a different host. You might need to modify your instance's host affinity to restart it on a different host. @@ -104 +104 @@ For these instances, we schedule instance stop events for 28 days from the date -For these instances, we schedule instance retirement events for 28 days from the date of the notification. At the date and time of the scheduled event, the instances are permanently terminated. We recommend that you manually launch replacement instances on the replacement host and then migrate the required data to the replacement instances before the scheduled event. +For these instances, instance retirement events are scheduled for 28 days from the date of the notification. At the date and time of the scheduled event, the instances are permanently terminated. We recommend that you manually launch replacement instances on the replacement host and then migrate the required data to the replacement instances before the scheduled event.