AWS Route53 Recovery Readiness
Read list cells, list resource sets, get cell readiness summary from Route53 Recovery Readiness (SigV4).
OCNORA ships 4 typed AWS Route53 Recovery Readiness 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 Readiness
- 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 Readiness
Operations, grouped by what they do to your data.
Read and search 3
Other operations 1
A sample AWS Route53 Recovery Readiness workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS Route53 Recovery Readiness trigger is needed.
- 2Get Cell Readiness Summaryroute53_recovery_readiness.get_cell_readiness_summaryGets readiness for a cell. Aggregates the readiness of all the resources that are associated with the cell into a single value.
- 3Write Actionroute53_recovery_readiness.callRun one of 16 write actions on Route53 Recovery Readiness.
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 16 write actions on Route53 Recovery Readiness.route53_recovery_readiness.call
- Get Cell Readiness SummaryGets readiness for a cell. Aggregates the readiness of all the resources that are associated with the cell into a single value.route53_recovery_readiness.get_cell_readiness_summary
- List CellsLists the cells for an account.route53_recovery_readiness.list_cells
- List Resource SetsLists the resource sets in an account.route53_recovery_readiness.list_resource_sets
AWS Route53 Recovery Readiness questions
- How does OCNORA authenticate with AWS Route53 Recovery Readiness?
- 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 Readiness?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS Route53 Recovery Readiness operation I need is not listed?
- Where AWS Route53 Recovery Readiness 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 Readiness?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS Route53 Recovery Readiness 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 Readiness 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.