AWS Lambda MicroVMs
Read list microvm images, list microvms, list microvm image versions from Lambda Microvms (SigV4).
OCNORA ships 4 typed AWS Lambda MicroVMs 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 Lambda MicroVMs
- 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 Lambda MicroVMs
Operations, grouped by what they do to your data.
Read and search 3
Other operations 1
A sample AWS Lambda MicroVMs workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS Lambda MicroVMs trigger is needed.
- 2List Microvm Image Versionslambda_microvms.list_microvm_image_versionsLists versions of a MicroVM image. We recommend using pagination to ensure that the operation returns quickly and successfully.
- 3Write Actionlambda_microvms.callRun one of 13 write actions on Lambda Microvms.
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 13 write actions on Lambda Microvms.lambda_microvms.call
- List Microvm Image VersionsLists versions of a MicroVM image. We recommend using pagination to ensure that the operation returns quickly and successfully.lambda_microvms.list_microvm_image_versions
- List Microvm ImagesLists MicroVM images in the account with optional name filtering.lambda_microvms.list_microvm_images
- List MicrovmsLists MicroVMs in the account with optional filtering by image and version.lambda_microvms.list_microvms
AWS Lambda MicroVMs questions
- How does OCNORA authenticate with AWS Lambda MicroVMs?
- 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 Lambda MicroVMs?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS Lambda MicroVMs operation I need is not listed?
- Where AWS Lambda MicroVMs 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 Lambda MicroVMs?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS Lambda MicroVMs 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 Lambda MicroVMs 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.