How does OCNORA authenticate with Amazon Elastic VMware Service?

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 Elastic VMware Service?

3 typed operations, each with a reference page listing its config fields and the shapes it emits.

What if the Amazon Elastic VMware Service operation I need is not listed?

Where Amazon Elastic VMware Service 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 Elastic VMware Service?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Amazon Elastic VMware Service 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.

Amazon Elastic VMware Service

Amazon Web ServicesAPI keyConnection test available

Read list environments, list environment connectors from evs (SigV4).

OCNORA ships 3 typed Amazon Elastic VMware Service 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.

Ask about Amazon Elastic VMware Service

Before you connect Amazon Elastic VMware Service

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 Elastic VMware Service

Operations, grouped by what they do to your data.

Read and search 2

Other operations 1

Write Action

A sample Amazon Elastic VMware Service workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Amazon Elastic VMware Service trigger is needed.
2
List Environment Connectorsevs.list_environment_connectors
Lists the connectors within an environment. Returns the status of each connector and its applicable checks, among other connector details.
3
Write Actionevs.call
Run one of 13 write actions on evs.

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 3