How does OCNORA authenticate with Amazon AppStream?

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 AppStream?

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

What if the Amazon AppStream operation I need is not listed?

Where Amazon AppStream 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 AppStream?

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

How are Amazon AppStream 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 AppStream

Amazon Web ServicesAPI keyConnection test available

Read describe fleets, describe image builders, describe users from AppStream (SigV4).

OCNORA ships 4 typed Amazon AppStream 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 AppStream

Before you connect Amazon AppStream

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 AppStream

Operations, grouped by what they do to your data.

Read and search 3

Other operations 1

Write Action

A sample Amazon AppStream workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Amazon AppStream trigger is needed.
2
Describe Fleetsappstream.describe_fleets
Retrieves a list that describes one or more specified fleets, if the fleet names are provided. Otherwise, all fleets in the account are described.
3
Write Actionappstream.call
Run one of 64 write actions on AppStream.

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