# Amazon OpenSearch Service Canonical: https://inetgeek.com/search/amazon-opensearch/ Managed OpenSearch in two deployment models: provisioned instances billed by the hour, or serverless billed by compute unit. ## Who it suits An estate already on AWS. Two deployment models under one service — instances you size and reserve, or serverless compute units — with reserved pricing and savings plans available, and IAM, KMS and VPC integration that needs no extra wiring. Consider something else if You want a price you can read off a page. The serverless rate renders as a template placeholder filled in by an API, and the only figure on the pricing page is inside a worked example; vector search is also billed as its own collection type that cannot share compute with keyword search. ## iScore 59 / 100 (80% interval 52–66), rank 4 of 5 in search — interval overlaps the next rank, so this is an ordering, not a finding. inetGeek's own reading, computed from sourced facts against category peers by disclosed rules. Not a provider claim. Intervals are 80%; a provider with few documented facts is pulled toward the category middle rather than scored on what little is known. Method: https://inetgeek.com/iscore/. Full output with every criterion's basis: https://inetgeek.com/scores.json. Every search peer ranked: https://inetgeek.com/search/amazon-opensearch/alternatives/ - Price: 8 (0–35), weight 36%, 1 of 2 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: free_offer_type - Capabilities: 90 (84–97), weight 29%, 2 of 2 criteria scored - Trust and compliance: 95 (89–100), weight 21%, 0 of 10 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: customer_managed_keys, dedicated_infrastructure, encryption_at_rest, gdpr_data_residency, hipaa_eligible, iso27001, pci_dss, private_networking, rbac, soc2 - Evidence: 70 (70–70), weight 14%, 4 of 4 criteria scored ## What the documentation says ### Pricing - Free tier: No ([source](https://aws.amazon.com/opensearch-service/pricing/), read 2026-09-15) - Entry paid plan: $0.24 per OCU-hour for serverless, and that figure is quoted from a worked example on the page rather than from its price table — the table renders the rate as a template placeholder filled in by a pricing API. No monthly minimum is published for either model. ([source](https://aws.amazon.com/opensearch-service/pricing/), read 2026-09-15) - Pricing model: Two models, billed differently. Provisioned instances are on-demand, reserved or under a savings plan. Serverless bills compute and storage separately, with compute measured in OpenSearch Compute Units that cover CPU, memory and I/O for indexing or querying. ([source](https://aws.amazon.com/opensearch-service/pricing/), read 2026-09-15) ### Observability - Self-hostable: Supported ([source](https://aws.amazon.com/opensearch-service/pricing/), read 2026-09-15) ### Vector - Hybrid search (vector + keyword): Supported, and billed as a separate workload: a vector search collection cannot share compute units with a search or time-series collection, even under the same KMS key. ([source](https://aws.amazon.com/opensearch-service/pricing/), read 2026-09-15) ### Compliance - Dedicated infrastructure: Provisioned deployments run on instances you size and reserve; serverless does not expose an instance at all and scales compute units instead. ([source](https://aws.amazon.com/opensearch-service/pricing/), read 2026-09-15) ## Compared with - [Amazon OpenSearch Service vs Algolia](https://inetgeek.com/compare/algolia-vs-amazon-opensearch/) - [Amazon OpenSearch Service vs Meilisearch](https://inetgeek.com/compare/meilisearch-vs-amazon-opensearch/) - [Amazon OpenSearch Service vs Typesense](https://inetgeek.com/compare/typesense-vs-amazon-opensearch/)