AWS IoT Greengrass V2
Read list deployments, list components, list component versions from GreengrassV2 (SigV4).
OCNORA ships 4 typed AWS IoT Greengrass V2 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 Greengrass V2
- 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 Greengrass V2
Operations, grouped by what they do to your data.
Read and search 3
Other operations 1
A sample AWS IoT Greengrass V2 workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS IoT Greengrass V2 trigger is needed.
- 2List Component Versionsgreengrassv2.list_component_versionsRetrieves a paginated list of all versions for a component. Greater versions are listed first.
- 3Write Actiongreengrassv2.callRun one of 14 write actions on GreengrassV2.
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 GreengrassV2.greengrassv2.call
- List Component VersionsRetrieves a paginated list of all versions for a component. Greater versions are listed first.greengrassv2.list_component_versions
- List ComponentsRetrieves a paginated list of component summaries. This list includes components that you have permission to view.greengrassv2.list_components
- List DeploymentsRetrieves a paginated list of deployments.greengrassv2.list_deployments
AWS IoT Greengrass V2 questions
- How does OCNORA authenticate with AWS IoT Greengrass V2?
- 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 Greengrass V2?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS IoT Greengrass V2 operation I need is not listed?
- Where AWS IoT Greengrass V2 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 Greengrass V2?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS IoT Greengrass V2 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 Greengrass V2 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.