AWS IoT Core Device Advisor
Read list suite definitions, list suite runs, get suite run report from IotDeviceAdvisor (SigV4).
OCNORA ships 4 typed AWS IoT Core Device Advisor 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 IoT Core Device Advisor
- 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 IoT Core Device Advisor
Operations, grouped by what they do to your data.
Read and search 3
Other operations 1
A sample AWS IoT Core Device Advisor workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS IoT Core Device Advisor trigger is needed.
- 2Get Suite Run Reportiotdeviceadvisor.get_suite_run_reportGets a report download link for a successful Device Advisor qualifying test suite run. Requires permission to access the GetSuiteRunReport action.
- 3Write Actioniotdeviceadvisor.callRun one of 7 write actions on IotDeviceAdvisor.
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 7 write actions on IotDeviceAdvisor.iotdeviceadvisor.call
- Get Suite Run ReportGets a report download link for a successful Device Advisor qualifying test suite run. Requires permission to access the GetSuiteRunReport action.iotdeviceadvisor.get_suite_run_report
- List Suite DefinitionsLists the Device Advisor test suites you have created. Requires permission to access the ListSuiteDefinitions action.iotdeviceadvisor.list_suite_definitions
- List Suite RunsLists runs of the specified Device Advisor test suite.iotdeviceadvisor.list_suite_runs
AWS IoT Core Device Advisor questions
- How does OCNORA authenticate with AWS IoT Core Device Advisor?
- 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 IoT Core Device Advisor?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS IoT Core Device Advisor operation I need is not listed?
- Where AWS IoT Core Device Advisor 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 IoT Core Device Advisor?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS IoT Core Device Advisor 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 IoT Core Device Advisor 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.