Amazon CloudWatch Application Signals
Read list service level objectives, list service level objective exclusion windows, list services from Application Signals (SigV4).
OCNORA ships 4 typed Amazon CloudWatch Application Signals operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Amazon CloudWatch Application Signals
- Authentication
- API key
- Credential
- {"access_key_id", "secret_access_key"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Amazon CloudWatch Application Signals
Operations, grouped by what they do to your data.
Read and search 3
Other operations 1
A sample Amazon CloudWatch Application Signals workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Amazon CloudWatch Application Signals trigger is needed.
- 2List Service Level Objective Exclusion Windowsapplication_signals.list_service_level_objective_exclusion_windowsRetrieves all exclusion windows configured for a specific SLO.
- 3Write Actionapplication_signals.callRun one of 13 write actions on Application Signals.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 4
- Write ActionRun one of 13 write actions on Application Signals.application_signals.call
- List Service Level Objective Exclusion WindowsRetrieves all exclusion windows configured for a specific SLO.application_signals.list_service_level_objective_exclusion_windows
- List Service Level ObjectivesReturns a list of SLOs created in this account.application_signals.list_service_level_objectives
- List ServicesReturns a list of services that have been discovered by Application Signals.application_signals.list_services
Amazon CloudWatch Application Signals questions
- How does OCNORA authenticate with Amazon CloudWatch Application Signals?
- With a stored API key credential, shaped {"access_key_id", "secret_access_key"}. A connection test can check it when you add it.
- What can I automate with Amazon CloudWatch Application Signals?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Amazon CloudWatch Application Signals operation I need is not listed?
- Where Amazon CloudWatch Application Signals has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Amazon CloudWatch Application Signals?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Amazon CloudWatch Application Signals calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Amazon CloudWatch Application Signals workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.