How does OCNORA authenticate with AWS Secrets Manager?

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 Secrets Manager?

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

What if the AWS Secrets Manager operation I need is not listed?

Where AWS Secrets Manager 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 Secrets Manager?

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

How are AWS Secrets Manager 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 Secrets Manager

Amazon Web ServicesAPI keyConnection test available

Read and write secrets in AWS Secrets Manager (SigV4).

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

Before you connect AWS Secrets Manager

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 Secrets Manager

Operations, grouped by what they do to your data.

A sample AWS Secrets Manager workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS Secrets Manager trigger is needed.
2
Get Secretsecrets_manager.get_secret_value
Read a secret's current value from AWS Secrets Manager.
3
Create Secretsecrets_manager.create_secret
Create a new secret with an initial value.

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