AWS CloudWatch Observability Access Manager
Read list links, list sinks, list attached links from OAM (SigV4).
OCNORA ships 4 typed AWS CloudWatch Observability Access Manager 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 Access Manager
- 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 Access Manager
Operations, grouped by what they do to your data.
Read and search 3
Other operations 1
A sample AWS CloudWatch Observability Access Manager workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS CloudWatch Observability Access Manager trigger is needed.
- 2List Attached Linksoam.list_attached_linksReturns a list of source account links that are linked to this monitoring account sink.
- 3Write Actionoam.callRun one of 8 write actions on OAM.
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 8 write actions on OAM.oam.call
- List Attached LinksReturns a list of source account links that are linked to this monitoring account sink.oam.list_attached_links
- List LinksUse this operation in a source account to return a list of links to monitoring account sinks that this source account has.oam.list_links
- List SinksUse this operation in a monitoring account to return the list of sinks created in that account.oam.list_sinks
AWS CloudWatch Observability Access Manager questions
- How does OCNORA authenticate with AWS CloudWatch Observability Access Manager?
- 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 Access Manager?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS CloudWatch Observability Access Manager operation I need is not listed?
- Where AWS CloudWatch Observability Access Manager 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 Access Manager?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS CloudWatch Observability Access Manager 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 Access Manager 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.