Amazon OpenSearch Ingestion
Read list pipelines, list pipeline endpoints, get pipeline change progress from OSIS (SigV4).
OCNORA ships 4 typed Amazon OpenSearch Ingestion 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.
Before you connect Amazon OpenSearch Ingestion
- 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 OpenSearch Ingestion
Operations, grouped by what they do to your data.
Read and search 3
Other operations 1
A sample Amazon OpenSearch Ingestion workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Amazon OpenSearch Ingestion trigger is needed.
- 2Get Pipeline Change Progressosis.get_pipeline_change_progressReturns progress information for the current change happening on an OpenSearch Ingestion pipeline.
- 3Write Actionosis.callRun one of 13 write actions on OSIS.
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 4
- Write ActionRun one of 13 write actions on OSIS.osis.call
- Get Pipeline Change ProgressReturns progress information for the current change happening on an OpenSearch Ingestion pipeline.osis.get_pipeline_change_progress
- List Pipeline EndpointsLists all pipeline endpoints in your account.osis.list_pipeline_endpoints
- List PipelinesLists all OpenSearch Ingestion pipelines in the current Amazon Web Services account and Region.osis.list_pipelines
Amazon OpenSearch Ingestion questions
- How does OCNORA authenticate with Amazon OpenSearch Ingestion?
- 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 OpenSearch Ingestion?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Amazon OpenSearch Ingestion operation I need is not listed?
- Where Amazon OpenSearch Ingestion 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 OpenSearch Ingestion?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Amazon OpenSearch Ingestion 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.
See your first Amazon OpenSearch Ingestion workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.