List Service Level Objective Exclusion Windows

application_signals.list_service_level_objective_exclusion_windows
ActionAmazon Web Servicesconnection required

Calls the AWS application_signals API (SigV4).

Retrieves all exclusion windows configured for a specific SLO.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Amazon CloudWatch Application Signals
Secret shape
{"access_key_id", "secret_access_key"}
Config it needs
region
Resolved by
config.connection_id, else node.connection_id

Configuration

4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
region
AWS region (overrides the connection).
stringNo———
id
The ID of the SLO to list exclusion windows for.
stringYes———
max_results
Maximum items to return.
numberNo50≥ 1—
next_token
Continues a previous run of this node: pass that run's paging token here. Leave blank to start at the first page.
stringNo———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "max_results": 50
}

Output

One shape.

result

FieldTypeExample
ExclusionWindows
array—
NextToken
string—
{
  "ExclusionWindows": [],
  "NextToken": ""
}

Related Amazon CloudWatch Application Signals nodes

See List Service Level Objective Exclusion Windows run in a workflow.

In a technical demo we add the Amazon CloudWatch Application Signals connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.