Amazon Route 53 Global Resolver
Read list firewall rules, list d n s views, list access sources from Route53GlobalResolver (SigV4).
OCNORA ships 4 typed Amazon Route 53 Global Resolver 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 Amazon Route 53 Global Resolver
- 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 Amazon Route 53 Global Resolver
Operations, grouped by what they do to your data.
Read and search 3
Other operations 1
A sample Amazon Route 53 Global Resolver workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Amazon Route 53 Global Resolver trigger is needed.
- 2List Access Sourcesroute53globalresolver.list_access_sourcesLists all access sources with pagination support.
- 3Write Actionroute53globalresolver.callRun one of 29 write actions on Route53GlobalResolver.
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 29 write actions on Route53GlobalResolver.route53globalresolver.call
- List Access SourcesLists all access sources with pagination support.route53globalresolver.list_access_sources
- List D N S ViewsLists all DNS views for a Route 53 Global Resolver with pagination support.route53globalresolver.list_dns_views
- List Firewall RulesLists all DNS firewall rules for a DNS view with pagination support.route53globalresolver.list_firewall_rules
Amazon Route 53 Global Resolver questions
- How does OCNORA authenticate with Amazon Route 53 Global Resolver?
- 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 Amazon Route 53 Global Resolver?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Amazon Route 53 Global Resolver operation I need is not listed?
- Where Amazon Route 53 Global Resolver 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 Amazon Route 53 Global Resolver?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Amazon Route 53 Global Resolver 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 Amazon Route 53 Global Resolver 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.