AWS Route53 Recovery Control Config
Read list clusters, list control panels, list safety rules from Route53 Recovery Control Config (SigV4).
OCNORA ships 4 typed AWS Route53 Recovery Control Config 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 Control Config
- 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 Control Config
Operations, grouped by what they do to your data.
Read and search 3
Other operations 1
A sample AWS Route53 Recovery Control Config workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS Route53 Recovery Control Config trigger is needed.
- 2List Clustersroute53_recovery_control_config.list_clustersReturns an array of all the clusters in an account.
- 3Write Actionroute53_recovery_control_config.callRun one of 14 write actions on Route53 Recovery Control Config.
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 14 write actions on Route53 Recovery Control Config.route53_recovery_control_config.call
- List ClustersReturns an array of all the clusters in an account.route53_recovery_control_config.list_clusters
- List Control PanelsReturns an array of control panels in an account or in a cluster.route53_recovery_control_config.list_control_panels
- List Safety RulesList the safety rules (the assertion rules and gating rules) that you've defined for the routing controls in a control panel.route53_recovery_control_config.list_safety_rules
AWS Route53 Recovery Control Config questions
- How does OCNORA authenticate with AWS Route53 Recovery Control Config?
- 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 Control Config?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS Route53 Recovery Control Config operation I need is not listed?
- Where AWS Route53 Recovery Control Config 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 Control Config?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS Route53 Recovery Control Config 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 Control Config 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.