How does OCNORA authenticate with Amazon Security Lake?

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 Security Lake?

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

What if the Amazon Security Lake operation I need is not listed?

Where Amazon Security Lake 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 Security Lake?

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

How are Amazon Security Lake 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 Security Lake

Amazon Web ServicesAPI keyConnection test available

Read list subscribers, list data lakes from SecurityLake (SigV4).

OCNORA ships 3 typed Amazon Security Lake 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 Security Lake

Before you connect Amazon Security Lake

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 Security Lake

Operations, grouped by what they do to your data.

Read and search 2

Other operations 1

Write Action

A sample Amazon Security Lake workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Amazon Security Lake trigger is needed.
2
List Data Lakessecuritylake.list_data_lakes
Retrieves the Amazon Security Lake configuration object for the specified Amazon Web Services Regions.
3
Write Actionsecuritylake.call
Run one of 22 write actions on SecurityLake.

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