How does OCNORA authenticate with Amazon SageMaker Feature Store Runtime?

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 SageMaker Feature Store Runtime?

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

What if the Amazon SageMaker Feature Store Runtime operation I need is not listed?

Where Amazon SageMaker Feature Store Runtime 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 SageMaker Feature Store Runtime?

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

How are Amazon SageMaker Feature Store Runtime 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 SageMaker Feature Store Runtime

Amazon Web ServicesAPI keyConnection test available

Read list records from SageMaker FeatureStore Runtime (SigV4).

OCNORA ships 2 typed Amazon SageMaker Feature Store Runtime 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 SageMaker Feature Store Runtime

Before you connect Amazon SageMaker Feature Store Runtime

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 SageMaker Feature Store Runtime

Operations, grouped by what they do to your data.

Read and search 1

List Records

Other operations 1

Write Action

A sample Amazon SageMaker Feature Store Runtime workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Amazon SageMaker Feature Store Runtime trigger is needed.
2
List Recordssagemaker_featurestore_runtime.list_records
Lists the RecordIdentifier values of all records stored in a FeatureGroup's OnlineStore.
3
Write Actionsagemaker_featurestore_runtime.call
Run one of 3 write actions on SageMaker FeatureStore Runtime.

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