Amazon OpenSearch Ingestion vs Splunk Edge Processor

Amazon OpenSearch Ingestion is a managed, serverless service that streams logs, metrics, and traces to OpenSearch Service domains or OpenSearch Serverless collections. Each pipeline has a source, optional ordered processors, and one or more sinks, including another pipeline as a sink. Processing can filter, enrich, transform, normalize, aggregate, and route structured or unstructured data, including textual, numerical, and geospatial content. AWS automatically scales ingestion workloads and manages installation, patching, version upgrades, continuous monitoring, and repair. Users define YAML pipelines through the AWS Console or CLI, set minimum and maximum ingestion OCU capacity, or pause a pipeline; paused pipelines consume no OCUs. Billing is hourly with per-minute granularity for allocated OCUs, with one OCU providing 15 GB RAM and 2 vCPU. Private connectivity is available through VPC access and PrivateLink, or pipelines can use the public internet. Redaction, obfuscation, conditional routing, and a stated 99.9% availability SLA are included.

Splunk Edge Processor has no write-up on Specifiction yet; its figures are above.