How does OCNORA authenticate with AWS Sustainability?

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

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

What if the AWS Sustainability operation I need is not listed?

Where AWS Sustainability 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 Sustainability?

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

How are AWS Sustainability 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 Sustainability

Amazon Web ServicesAPI keyConnection test available

Read get estimated carbon emissions, get estimated water allocation, get estimated carbon emissions dimension values from Sustainability (SigV4).

OCNORA ships 3 typed AWS Sustainability 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 Sustainability

Before you connect AWS Sustainability

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 Sustainability

Operations, grouped by what they do to your data.

Read and search 3

A sample AWS Sustainability workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS Sustainability trigger is needed.
2
Get Estimated Carbon Emissionssustainability.get_estimated_carbon_emissions
Returns estimated carbon emission values based on customer grouping and filtering parameters.

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