Schedule maintenance windows for ECS instances

Usage notes

• Do not configure maintenance windows for instance maintenance attributes when using ECS scheduled maintenance windows.

• All time ranges use UTC. For a weekly (Every) schedule, the earliest start time is 00:00 on Sunday, and each end time must be later than the start time.

• Each maintenance window must span at least 4 hours in total.

• Each maintenance window can target only one scope: all instances in your account, instances in a specific resource group, or instances with specific tags.

• To prevent an instance from being maintained multiple times in a short period, configure the Minimum Interval Duration for the maintenance window. Valid values: 1 to 48 hours.

How it works

• Maintenance window takes effect: When a scheduled O&M event matches the maintenance window schedule, the task runs within the window.

  

• Maintenance window does not take effect: When a scheduled O&M event does not match any maintenance window, the task runs on the event's own schedule. Specify multiple time ranges to increase match coverage.

  

Maintenance actions

Maintenance windows support three actions: Restart Instance, Redeploy Instance, and Performance Jitter, No Restart. Redeploy Instance (high priority) overrides Restart Instance (low priority) — when a window with Redeploy Instance takes effect, matching SystemMaintenance.Reboot events are also executed within the window.

By default, scheduled O&M events expire after 48 hours. To extend the expiration period to 7 days, submit a ticket.

Create a maintenance window

1. Go to ECS console - Events.

2. On the Event page, choose Scheduled Maintenance Windows in the left-side navigation pane.

   

3. Click Create Maintenance Window.

4. In the Create Maintenance Window dialog box, configure the following parameters.

   Parameter	Description	Example
   Window Name	The window name. 2 to 200 characters; supports letters, digits, colons (:), underscores (_), periods (.), and hyphens (-). Keep the name within 2 to 64 characters to ensure full display. Duplicate names are allowed. Use unique names for easier management.	Redis maintenance window
   Resource Scope	The target scope. Each window supports only one scope type: All: All instances in your account. By Resource Group: All instances in a specific resource group. By Instance Tags: All instances with specific tags across all regions.	All
   Recurrence Frequency	The recurrence frequency: daily or weekly. Every: Weekly schedule. Every Day: Daily schedule.	Every Week
   Time Range	One or more time ranges in the schedule. Note Each time range must be at least 4 hours long.	Every Week: Start Time: Monday 0:00 End Time: Monday 4:00 Every Day: Start Time: 0:00 End Time: 4:00
   Maintenance Action	The maintenance action for event responses: Restart Instance: Restarts instances. Responds to SystemMaintenance.Reboot events only. Redeploy Instance: Redeploys and restarts instances. Responds to both SystemMaintenance.Reboot and SystemMaintenance.Redeploy events. Performance Jitter, No Restart: Allows brief performance jitter during system maintenance without triggering an instance restart or redeployment. This option has the least impact on your workloads and suits scenarios that require high service continuity and can tolerate short performance fluctuations.	Restart Instance
   Minimum Interval Duration	The minimum time interval between two consecutive scheduled O&M events on the same instance, used to prevent an instance from being maintained multiple times in a short period. Valid values: 1 to 48 hours. Default value: 1 hour. This parameter is in the More collapsible section of the dialog box; expand the section to configure it. After you set this parameter, if the next scheduled O&M event on the instance is triggered before the minimum interval elapses, the event is automatically postponed to the next available maintenance window after the interval ends. Note The Minimum Interval Duration applies only to scheduled O&M events. Emergency O&M events, such as security vulnerability fixes, are not subject to this interval.	24 Hours
   Effectiveness	Enable or disable the maintenance window. Turn on to enable. Turn off to disable.	Turn on the switch

   

5. Click OK.

Manage maintenance windows

• View maintenance windows. View the list on the Scheduled Maintenance Windows page, or click Details in the Actions column to view details.

  On the maintenance window management page, click Create Maintenance Window to create a new window. The list displays columns such as Maintenance Window ID/Name, Effectiveness, Recurrence Frequency, Supported Maintenance Actions, Minimum Interval Duration, Instance Scope, and Modification Time.

• Modify a maintenance window. When business requirements change (for example, the window conflicts with a business peak, or the window duration needs to be extended), find the target window and click Modify in the Actions column to update the configuration.

  In the dialog box that opens, you can modify the following parameters:

  • Window Name

  • Resource Scope (supports All, By Resource Group, and By Instance Tags)

  • Recurrence Frequency (for example, Every Day)

  • Time Range

  • Maintenance Action

  • Minimum Interval Duration

  • Effectiveness

• Delete a maintenance window. Delete redundant or overlapping windows. Find the target window and click Delete in the Actions column, then click OK in the confirmation dialog box to delete the maintenance window.