How does OCNORA authenticate with AWS RDS DataService?

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 RDS DataService?

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

What if the AWS RDS DataService operation I need is not listed?

Where AWS RDS DataService 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 RDS DataService?

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

How are AWS RDS DataService 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 RDS DataService

Amazon Web ServicesAPI keyConnection test available

Read execute statement from RDS Data (SigV4).

OCNORA ships 2 typed AWS RDS DataService 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 RDS DataService

Before you connect AWS RDS DataService

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 RDS DataService

Operations, grouped by what they do to your data.

Create and send 1

Execute Statement

Other operations 1

Write Action

A sample AWS RDS DataService workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS RDS DataService trigger is needed.
2
Write Actionrds_data.call
Run one of 5 write actions on RDS Data.

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 2