How does OCNORA authenticate with AWS Well-Architected Tool?

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 Well-Architected Tool?

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

What if the AWS Well-Architected Tool operation I need is not listed?

Where AWS Well-Architected Tool 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 Well-Architected Tool?

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

How are AWS Well-Architected Tool 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.

AWS Well-Architected Tool

Amazon Web ServicesAPI keyConnection test available

Read list agent profiles, list profiles, list agent goals from WellArchitected (SigV4).

OCNORA ships 4 typed AWS Well-Architected Tool 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 AWS Well-Architected Tool

Before you connect AWS Well-Architected Tool

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 Well-Architected Tool

Operations, grouped by what they do to your data.

Read and search 3

Other operations 1

Write Action

A sample AWS Well-Architected Tool workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS Well-Architected Tool trigger is needed.
2
List Lenseswellarchitected.list_lenses
List the available lenses.
3
Write Actionwellarchitected.call
Run one of 51 write actions on WellArchitected.

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