AWS mediaconnect documentation change
Summary
Restructured maintenance documentation to cover both flows and router I/Os, added details about maintenance windows, removed specific date selection process, and reorganized topics.
Security assessment
The changes focus on operational improvements for maintenance scheduling and resource management. While maintenance includes security patching, there's no evidence addressing a specific vulnerability. Updates emphasize minimizing disruption through maintenance windows and availability strategies.
Diff
diff --git a/mediaconnect/latest/ug/maintenance.md b/mediaconnect/latest/ug/maintenance.md index ad39707d7..d938a4fb0 100644 --- a//mediaconnect/latest/ug/maintenance.md +++ b//mediaconnect/latest/ug/maintenance.md @@ -7 +7 @@ -# MediaConnect flow maintenance +# Maintenance in MediaConnect @@ -9 +9 @@ -AWS Elemental MediaConnect routinely performs maintenance on underlying systems for security, reliability, and operational performance. The maintenance activities include actions such as patching the operating system, updating drivers, or installing software and patches. +AWS Elemental MediaConnect routinely performs maintenance on underlying systems for security, reliability, and operational performance. These maintenance activities include actions such as patching the operating system, updating drivers, and installing software updates. @@ -11 +11 @@ AWS Elemental MediaConnect routinely performs maintenance on underlying systems -###### Note +Maintenance applies to both router I/Os (inputs and outputs) and flows. For active resources, MediaConnect interrupts the resource to apply updates. For idle resources, updates are applied automatically the next time the resource starts. @@ -13 +13 @@ AWS Elemental MediaConnect routinely performs maintenance on underlying systems -As part of the maintenance process, your flow must be restarted. +To minimize disruption, configure a _maintenance window_ for each resource. A maintenance window specifies the preferred day and start hour for maintenance to occur. The window duration is two hours. When you configure a window, MediaConnect automatically applies updates at a time within that window. @@ -15,3 +15 @@ As part of the maintenance process, your flow must be restarted. -You can select the day and time that maintenance events occur. This is called a _maintenance window_ and is used every time a maintenance event is required. If you need to change the day and time, you can edit the maintenance window. - -When maintenance is required for your flow, AWS will assign your flow a **Required by** date. If you do not have a maintenance window configured for the flow, visit [Setting maintenance windows](./setting-flow-maintenance.html). You can view the flows that require maintenance on the MediaConnect console or by using the AWS CLI, visit [Viewing flows that require maintenance](./viewing-flows-maintenance.html). When a **Required by** date has been assigned to your flow, you can select a specific date for that maintenance to occur. The selected **Maintenance date** will only apply to the next maintenance event. +###### Important @@ -19 +17 @@ When maintenance is required for your flow, AWS will assign your flow a **Requir -If you do not configure a maintenance window, AWS selects a maintenance window for you—automatically. We recommend that you set a maintenance window for each flow and allow MediaConnect to perform the restart automatically during that window. Allowing MediaConnect to perform the restart results in less downtime for your flow. If a flow requires maintenance and you choose to manually restart the flow, the status of that flow's maintenance will change to **Canceled**. The manually restarted flow will still apply the required updates, but you will not receive the **Completed successfully** status. Since you performed the restart manually, the maintenance is considered **Canceled** because MediaConnect no longer requires updates for that flow. +The two-hour window duration does not mean your resource is affected for two hours. MediaConnect applies updates at some point within the two-hour window. @@ -21 +19 @@ If you do not configure a maintenance window, AWS selects a maintenance window f -The duration of the maintenance window is two hours. +If you operate redundant resources for resilience—for example, redundant flows or router I/Os in different AWS Regions—select different maintenance windows for each redundant resource. Choosing different days or times prevents simultaneous patching of redundant resources and helps maintain availability during maintenance events. @@ -23 +21 @@ The duration of the maintenance window is two hours. -###### Important +###### Topics @@ -25 +23 @@ The duration of the maintenance window is two hours. -The two hour window duration does not mean the flow will be affected for two hours. The flow will perform a normal stop and start at some point within the two hour window. + * [How maintenance works](./how-maintenance-works.html) @@ -27 +25 @@ The two hour window duration does not mean the flow will be affected for two hou -Example: If you configure a flow's maintenance window **Start hour** to be 02:00, the flow will restart at some point between 02:00 and 04:00. + * [Viewing router I/O maintenance status](./viewing-router-io-maintenance.html) @@ -29 +27 @@ Example: If you configure a flow's maintenance window **Start hour** to be 02:00 -In the event that maintenance does not occur at the scheduled date and time, MediaConnect will reschedule it to occur in the following week’s maintenance window, or automatically set a new window if you don't have one configured. + * [Setting router I/O maintenance windows](./setting-router-io-maintenance.html) @@ -31 +29 @@ In the event that maintenance does not occur at the scheduled date and time, Med -###### Topics + * [Viewing flow maintenance status](./viewing-flows-maintenance.html) @@ -33 +31 @@ In the event that maintenance does not occur at the scheduled date and time, Med - * [Viewing MediaConnect flows that require maintenance](./viewing-flows-maintenance.html) + * [Setting flow maintenance windows](./setting-flow-maintenance.html) @@ -35 +33 @@ In the event that maintenance does not occur at the scheduled date and time, Med - * [Setting maintenance windows](./setting-flow-maintenance.html) + * [Manually restarting resources for maintenance](./manual-restart-maintenance.html) @@ -48 +46 @@ Using signal maps -Viewing flows that require maintenance +How maintenance works