Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

CreateMaintenanceWindowRequest

import type { CreateMaintenanceWindowRequest } from "https://aws-api.deno.dev/v0.3/services/ssm.ts?docs=full";
interface CreateMaintenanceWindowRequest {
AllowUnassociatedTargets: boolean;
ClientToken?: string | null;
Cutoff: number;
Description?: string | null;
Duration: number;
EndDate?: string | null;
Name: string;
Schedule: string;
ScheduleOffset?: number | null;
ScheduleTimezone?: string | null;
StartDate?: string | null;
Tags?: Tag[] | null;
}

§Properties

§
AllowUnassociatedTargets: boolean
[src]

Enables a maintenance window task to run on managed nodes, even if you haven't registered those nodes as targets. If enabled, then you must specify the unregistered managed nodes (by node ID) when you register a task with the maintenance window.

If you don't enable this option, then you must specify previously-registered targets when you register a task with the maintenance window.

§
ClientToken?: string | null
[src]

User-provided idempotency token.

§
Cutoff: number
[src]

The number of hours before the end of the maintenance window that Amazon Web Services Systems Manager stops scheduling new tasks for execution.

§
Description?: string | null
[src]

An optional description for the maintenance window. We recommend specifying a description to help you organize your maintenance windows.

§
Duration: number
[src]

The duration of the maintenance window in hours.

§
EndDate?: string | null
[src]

The date and time, in ISO-8601 Extended format, for when you want the maintenance window to become inactive. EndDate allows you to set a date and time in the future when the maintenance window will no longer run.

§
Name: string
[src]

The name of the maintenance window.

§
Schedule: string
[src]

The schedule of the maintenance window in the form of a cron or rate expression.

§
ScheduleOffset?: number | null
[src]

The number of days to wait after the date and time specified by a cron expression before running the maintenance window.

For example, the following cron expression schedules a maintenance window to run on the third Tuesday of every month at 11:30 PM.

cron(30 23 ? * TUE#3 *)

If the schedule offset is 2, the maintenance window won't run until two days later.

§
ScheduleTimezone?: string | null
[src]

The time zone that the scheduled maintenance window executions are based on, in Internet Assigned Numbers Authority (IANA) format. For example: "America/Los_Angeles", "UTC", or "Asia/Seoul". For more information, see the Time Zone Database on the IANA website.

§
StartDate?: string | null
[src]

The date and time, in ISO-8601 Extended format, for when you want the maintenance window to become active. StartDate allows you to delay activation of the maintenance window until the specified future date.

§
Tags?: Tag[] | null
[src]

Optional metadata that you assign to a resource. Tags enable you to categorize a resource in different ways, such as by purpose, owner, or environment. For example, you might want to tag a maintenance window to identify the type of tasks it will run, the types of targets, and the environment it will run in. In this case, you could specify the following key-value pairs:

  • Key=TaskType,Value=AgentUpdate
    
  • Key=OS,Value=Windows
    
  • Key=Environment,Value=Production
    

Note: To add tags to an existing maintenance window, use the "AddTagsToResource" operation.