AWS Resource Explorer
Read list views, list resources, get resource explorer setup from Resource Explorer 2 (SigV4).
OCNORA ships 4 typed AWS Resource Explorer 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 Resource Explorer
- 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 Resource Explorer
Operations, grouped by what they do to your data.
Read and search 3
Other operations 1
A sample AWS Resource Explorer workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS Resource Explorer trigger is needed.
- 2Get Resource Explorer Setupresource_explorer_2.get_resource_explorer_setupRetrieves the status and details of a Resource Explorer setup operation.
- 3Write Actionresource_explorer_2.callRun one of 12 write actions on Resource Explorer 2.
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 12 write actions on Resource Explorer 2.resource_explorer_2.call
- Get Resource Explorer SetupRetrieves the status and details of a Resource Explorer setup operation.resource_explorer_2.get_resource_explorer_setup
- List ResourcesReturns a list of resources and their details that match the specified criteria.resource_explorer_2.list_resources
- List ViewsLists the Amazon resource names (ARNs) of the views available in the Amazon Web Services Region in which you call this operation.resource_explorer_2.list_views
AWS Resource Explorer questions
- How does OCNORA authenticate with AWS Resource Explorer?
- 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 Resource Explorer?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS Resource Explorer operation I need is not listed?
- Where AWS Resource Explorer 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 Resource Explorer?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS Resource Explorer 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 Resource Explorer 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.