Amazon OpenSearch Ingestion
Amazon OpenSearch Ingestion is a managed, serverless collector that streams logs, metrics, and traces in real time to OpenSearch Service domains and OpenSear…
What Amazon OpenSearch Ingestion is
Amazon OpenSearch Ingestion is a managed, serverless collector that streams logs, metrics, and traces in real time to OpenSearch Service domains and OpenSearch Serverless collections. A pipeline starts with a source, can apply processors in order, and sends results to one or more sinks, including another pipeline. Processing can filter, enrich, transform, normalize, aggregate, or route data before analysis and visualization. Supported inputs include structured and unstructured material, text, numbers, and geospatial data.
Users write pipeline configuration in YAML and create pipelines through the AWS Console or CLI. The service scales ingestion workloads automatically, while AWS manages installation, patching, upgrades, monitoring, and repair. Users can set minimum and maximum OCU capacity per pipeline or pause it; paused pipelines consume no OCUs. Billing is hourly with per-minute granularity for allocated ingestion OCUs, and one OCU provides 15 GB RAM and 2 vCPU. Connectivity can use VPC access through PrivateLink or public internet access. Built-in processors can redact or obscure sensitive information, and conditional routing can support data residency needs. The product page states an availability SLA of 99.9%.
Good
- Streams logs, metrics, and traces in real time
- Automatically scales ingestion workloads
- Pipelines can redact or obscure sensitive data
- Paused pipelines consume no OCUs
Watch out
- No free plan is listed
- Billing applies to allocated ingestion OCUs
- Pipelines require YAML configuration
Who it suits
This service suits teams collecting logs, metrics, or traces for OpenSearch analysis and visualization. It is also relevant where pipeline processing, capacity controls, or private connectivity are needed.
Verdict
OpenSearch Ingestion combines managed collection with configurable processing and OCU controls. Teams should consider its allocated-capacity billing and pipeline configuration needs before adopting it.
Plans and prices
From Amazon OpenSearch Ingestion's own pricing page, checked 8 Oct 2001.
| Plan | Price | What it gives you |
|---|---|---|
| Pay-as-you-go | Free | 1 OCU = 15 GB RAM and 2 vCPU · configure minimum and maximum OCUs per pipeline · paused pipelines consume no OCUs · Billed hourly with per-minute granularity for allocated ingestion OCUs. |
The facts
Each one read from Amazon OpenSearch Ingestion's own pages, with the date it was checked.
What it does
- Availability
- The product page states an availability SLA of 99.9%.checked 8 Oct 2001
- AWS origin
- AWS says it launched in 2006; its about page describes customers ranging from startups and enterprises to nonprofits and governments.checked 8 Oct 2001
- Configuration
- Users define pipeline configuration in YAML and can create pipelines through the AWS Console or AWS CLI.checked 8 Oct 2001
- Data processing
- Pipelines can filter, enrich, transform, normalize, aggregate, and route data before downstream analysis and visualization.checked 8 Oct 2001
- Data protection
- Built-in processors can redact or obfuscate sensitive information before it reaches a destination, and conditional routing can help meet data residency requirements.checked 8 Oct 2001
- Data types
- It supports structured, unstructured, textual, numerical, and geospatial data, including logs, metrics, and traces.checked 8 Oct 2001
- Integrations
- The service delivers data to OpenSearch domains and Serverless collections, and the AWS page names CyberArk, Calyptia, and Confluent as customers and partners.checked 8 Oct 2001
- Network security
- Pipelines can use VPC access through PrivateLink for private connectivity or public access over the internet.checked 8 Oct 2001
- Pipeline structure
- A pipeline uses a source, optional ordered processors, and one or more sinks, and sinks can include another pipeline.checked 8 Oct 2001
- Purpose
- A fully managed, serverless data collector streams real-time logs, metrics, and traces to OpenSearch Service domains and OpenSearch Serverless collections.checked 8 Oct 2001
- Scaling and operations
- The service automatically scales ingestion workloads and AWS manages software installation, patching, version upgrades, and 24x7 monitoring and repair.checked 8 Oct 2001
- Security model
- AWS describes security as a shared responsibility and documents VPC access, cross-account ingestion, IAM, CloudTrail logging, and PrivateLink controls.checked 8 Oct 2001
- Supported Data Prepper
- The developer guide says OpenSearch Ingestion supports Data Prepper 2.x and currently provisions pipelines with version 2.7.checked 8 Oct 2001
Money
- Cost controls
- Users can set minimum and maximum OCU capacity per pipeline and pause a pipeline; paused pipelines consume no OCUs.checked 8 Oct 2001
Alternatives to Amazon OpenSearch Ingestion
- 1
Telegraf
Free planOpen sourceWebAPILinuxmacOS8.2From $1,500 a month - 2
syslog-ng
Free planOpen sourceAPILinuxmacOSSelf-hosted8.0$2,800, paid once - 3
Honeycomb
Free planAndroidiOSWebAPI7.4From $150 a month - 4
Edge Delta
Free planWebAPILinuxmacOS7.0From $20 a month - 5
Bindplane
Free planWebAPILinuxSelf-hosted6.8From $499 a month - 6
NXLog
Free planWebWindowsmacOSLinux6.8From $12.12 a month