AWS CloudWatch Observability Admin Service
Read list telemetry pipelines, list telemetry rules, get telemetry rule for organization from ObservabilityAdmin (SigV4).
OCNORA ships 4 typed AWS CloudWatch Observability Admin Service 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 AWS CloudWatch Observability Admin Service
- 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 AWS CloudWatch Observability Admin Service
Operations, grouped by what they do to your data.
Other operations 1
A sample AWS CloudWatch Observability Admin Service workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS CloudWatch Observability Admin Service trigger is needed.
- 2Get Telemetry Rule For Organizationobservabilityadmin.get_telemetry_rule_for_organizationRetrieves the details of a specific organization telemetry rule.
- 3Write Actionobservabilityadmin.callRun one of 24 write actions on ObservabilityAdmin.
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 24 write actions on ObservabilityAdmin.observabilityadmin.call
- Get Telemetry Rule For OrganizationRetrieves the details of a specific organization telemetry rule.observabilityadmin.get_telemetry_rule_for_organization
- List Telemetry PipelinesReturns a list of telemetry pipelines in your account.observabilityadmin.list_telemetry_pipelines
- List Telemetry RulesLists all telemetry rules in your account. You can filter the results by specifying a rule name prefix.observabilityadmin.list_telemetry_rules
AWS CloudWatch Observability Admin Service questions
- How does OCNORA authenticate with AWS CloudWatch Observability Admin Service?
- 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 AWS CloudWatch Observability Admin Service?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS CloudWatch Observability Admin Service operation I need is not listed?
- Where AWS CloudWatch Observability Admin Service 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 AWS CloudWatch Observability Admin Service?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS CloudWatch Observability Admin Service 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 AWS CloudWatch Observability Admin Service 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.