AWS Route53 Recovery Cluster
Read list routing controls, get routing control state from Route53 Recovery Cluster (SigV4).
OCNORA ships 3 typed AWS Route53 Recovery Cluster 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 Route53 Recovery Cluster
- 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 Route53 Recovery Cluster
Operations, grouped by what they do to your data.
Read and search 2
Other operations 1
A sample AWS Route53 Recovery Cluster workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS Route53 Recovery Cluster trigger is needed.
- 2Get Routing Control Stateroute53_recovery_cluster.get_routing_control_stateGet the state for a routing control.
- 3Write Actionroute53_recovery_cluster.callRun one of 2 write actions on Route53 Recovery Cluster.
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 3
- Write ActionRun one of 2 write actions on Route53 Recovery Cluster.route53_recovery_cluster.call
- Get Routing Control StateGet the state for a routing control.route53_recovery_cluster.get_routing_control_state
- List Routing ControlsList routing control names and Amazon Resource Names (ARNs), as well as the routing control state for each routing control, along with the control panel name and control panel ARN for the routing controls.route53_recovery_cluster.list_routing_controls
AWS Route53 Recovery Cluster questions
- How does OCNORA authenticate with AWS Route53 Recovery Cluster?
- 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 Route53 Recovery Cluster?
- 3 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS Route53 Recovery Cluster operation I need is not listed?
- Where AWS Route53 Recovery Cluster 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 Route53 Recovery Cluster?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS Route53 Recovery Cluster 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 Route53 Recovery Cluster 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.