AWS CloudWatch RUM
Read list app monitors, list rum metrics destinations, batch get rum metric definitions from RUM (SigV4).
OCNORA ships 4 typed AWS CloudWatch RUM 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 RUM
- 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 RUM
Operations, grouped by what they do to your data.
Read and search 2
Other operations 2
A sample AWS CloudWatch RUM workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS CloudWatch RUM trigger is needed.
- 2List App Monitorsrum.list_app_monitorsReturns a list of the Amazon CloudWatch RUM app monitors in the account.
- 3Batch Get Rum Metric Definitionsrum.batch_get_rum_metric_definitionsRetrieves the list of metrics and dimensions that a RUM app monitor is sending to a single destination.
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
- Batch Get Rum Metric DefinitionsRetrieves the list of metrics and dimensions that a RUM app monitor is sending to a single destination.rum.batch_get_rum_metric_definitions
- Write ActionRun one of 13 write actions on RUM.rum.call
- List App MonitorsReturns a list of the Amazon CloudWatch RUM app monitors in the account.rum.list_app_monitors
- List Rum Metrics DestinationsReturns a list of destinations that you have created to receive RUM extended metrics, for the specified app monitor.rum.list_rum_metrics_destinations
AWS CloudWatch RUM questions
- How does OCNORA authenticate with AWS CloudWatch RUM?
- 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 RUM?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS CloudWatch RUM operation I need is not listed?
- Where AWS CloudWatch RUM 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 RUM?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS CloudWatch RUM 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 RUM 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.