Hubbry Logo
OpenSearch (software)OpenSearch (software)Main
Open search
OpenSearch (software)
Community hub
OpenSearch (software)
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
OpenSearch (software)
OpenSearch (software)
OpenSearch (software)
View on Wikipedia
from Wikipedia
OpenSearch
Original authorAmazon Web Services
DeveloperOpenSearch Software Foundation
Initial release12 April 2021; 4 years ago (2021-04-12)
Stable release
3.3.2[1] / 30 October 2025; 25 days ago (30 October 2025)
Repositorygithub.com/opensearch-project/opensearch
Written inJava
TypeSearch engine
LicenseApache License 2.0
Websitewww.opensearch.org
OpenSearch Dashboards
DeveloperOpenSearch Software Foundation
Initial release12 April 2021; 4 years ago (2021-04-12)
Stable release
3.3.2[1] Edit this on Wikidata / 30 October 2025
Repositorygithub.com/opensearch-project/opensearch-dashboards
Written inTypeScript, JavaScript
TypeSearch engine
LicenseApache License 2.0
Websitewww.opensearch.org

OpenSearch is a family of software consisting of a search engine (also named OpenSearch), and OpenSearch Dashboards, a data visualization dashboard for that search engine.[2] It is an open-source project developed by the OpenSearch Software Foundation (a Linux Foundation project) written primarily in Java.

As of August 2024, AWS reported that OpenSearch had "tens of thousands" of customers,[3] while Elastic claimed to have over 20,000 subscribers.[4] In the preceding year, OpenSearch had about 50 monthly contributors[5] while ElasticSearch had between 70 and 90.[6]

History

[edit]

The project was created in 2021 by Amazon Web Services[7][8][2][9][10] as a fork of Elasticsearch and Kibana after Elastic NV changed the license of new versions of this software away from the open-source Apache License in favour of the Server Side Public License (SSPL).[11][12][8][2] Amazon would hold sole ownership status and write access to the source code repositories, but invited pull requests from anyone.[2][7] Other companies such as Logz.io, CrateDB, Red Hat and others announced an interest in building or joining a community to continue using and maintaining this open-source software.[12][13][8][14]

On September 16, 2024, the Linux Foundation and Amazon Web Services announced the creation of the OpenSearch Software Foundation.[15][16] Ownership of OpenSearch software was transferred from Amazon to OpenSearch Software Foundation, which is organized as an open technical project within the Linux Foundation. The Linux Foundation reported that at the time, "OpenSearch recorded more than 700 million software downloads and participation from thousands of contributors and more than 200 project maintainers." The OpenSearch Software Foundation would launch with support from premier members Amazon Web Services, SAP, and Uber.

Projects

[edit]

OpenSearch

[edit]

OpenSearch is a Lucene-based search engine that started as a fork of version 7.10.2 of the Elasticsearch service.[8][2] It has Elastic NV trademarks and telemetry removed. It is licensed under the Apache License, version 2,[2] without a Contributor License Agreement. The maintainers have made a commitment to remain completely compatible with Elasticsearch in its initial versions.[2]

OpenSearch Dashboards

[edit]

OpenSearch Dashboards started as a fork of version 7.10.2 of Elastic's Kibana software, and is also under the Apache License, version 2.[8][2][17]

See also

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

OpenSearch (software)

View on Grokipedia
from Grokipedia
OpenSearch is a distributed, community-driven, Apache 2.0-licensed open-source search and analytics suite forked from version 7.10.2, enabling scalable ingestion, , visualization, and analysis of diverse data types including logs, metrics, and vectors. Launched in April 2021 by (AWS) and collaborators in response to Elastic NV's shift from the permissive to the more restrictive Elastic License 2.0 and (SSPL), OpenSearch preserves compatibility with Elasticsearch's APIs while fostering independent innovation under neutral governance. The project has evolved to include built-in features, SQL querying, alerting, and advanced capabilities like neural and hybrid search, supporting real-time monitoring, , and AI applications such as retrieval-augmented generation. OpenSearch Dashboards provides an intuitive interface for data exploration and dashboard creation, akin to but extended with plugins for and reporting. Its architecture relies on clusters of nodes managing for horizontal scaling and , handling petabyte-scale datasets across industries. Governed initially by AWS and now under the Linux Foundation's OpenSearch Software Foundation since September 2024, the suite has seen rapid adoption with downloads exceeding 700 million and year-over-year growth of 78%, though critics note occasional performance gaps in indexing speed compared to in certain benchmarks. The has sparked debates on open-source licensing , highlighting tensions between commercial interests and community-driven development, yet OpenSearch's commitment to Apache licensing ensures vendor-neutral extensibility via plugins and integrations.

Origins

Background on Elasticsearch Licensing Changes

Elasticsearch, originally released under the permissive Apache License 2.0, facilitated widespread adoption by allowing unrestricted use, modification, and distribution, including integration into managed cloud services offered by providers such as (AWS). This licensing model supported the software's growth into a dominant search and engine, with AWS launching Elasticsearch Service in 2015 based on the open-source codebase. The Apache 2.0 terms imposed no obligations on service providers to share revenues or modifications, enabling competitive offerings that contributed to Elasticsearch's ecosystem expansion. On January 21, 2021, announced a shift for versions 7.11 and later, relicensing the Apache 2.0 portions of and under a dual model of the and Elastic License 2.0 (ELv2). The SSPL, proposed by and not recognized as by the due to its requirement that managed service providers release their entire software stack as source-available, aimed to curb what Elastic described as "unfair" commercialization by hyperscalers offering as a service without equivalent contributions. Similarly, ELv2 permitted internal use and self-hosting but restricted document-level security features for competing cloud services unless users obtained a commercial subscription from Elastic. Elastic justified the change as a defense against cloud providers duplicating their technology stack—encompassing over 200 components—without reciprocity, citing AWS's Service as an example where Elastic received no revenue despite significant usage. Critics, including AWS and portions of the developer community, argued that the relicensing deviated from open-source principles by introducing copyleft-like restrictions that effectively limited forking and vendor-neutral adoption, potentially leading to greater under Elastic's control rather than empowering users. This backlash manifested in concerns over reduced freedoms, with projects like SkyWalking publicly decrying the move as closing off collaborative development under OSI-approved terms. In response, AWS committed to maintaining the final 2.0 release, version 7.10.2, as a community-driven alternative to preserve permissive licensing and mitigate risks of proprietary drift.

AWS Fork and Initial Launch

In April 2021, Amazon Web Services initiated the OpenSearch project by forking Elasticsearch version 7.10.2 and Kibana version 7.10.2, establishing a community-driven open-source alternative licensed under the permissive Apache 2.0 terms. This fork preserved the core search, indexing, and analytics engine capabilities of the original projects while committing AWS to ongoing development without restrictive licensing constraints. The immediate objective was to enable seamless continuity for users reliant on open-source distributions, avoiding dependencies on Elastic's subsequent dual-licensing model that combined Apache 2.0 with the more proprietary Server Side Public License for versions beyond 7.10.2. The forked codebase, rebranded as OpenSearch for the backend and OpenSearch Dashboards for the visualization interface, retained foundational components such as Lucene-based , distributed querying, and real-time data ingestion to ensure with existing 7.10.2 deployments. Initial enhancements focused on stabilizing the branch for community contributions, with AWS pledging resources for maintenance and feature parity to the pre-fork baseline, rather than introducing divergent AWS-centric modifications at inception. On July 12, 2021, OpenSearch 1.0 achieved production readiness, marking the project's first stable release and fulfilling the goal of delivering a viable, independently evolving suite. Concurrently, AWS integrated OpenSearch into its managed cloud offerings by renaming Amazon Elasticsearch Service to Amazon OpenSearch Service and adding support for OpenSearch 1.0 on September 8, 2021, thereby providing a fully managed environment that prioritized operational compatibility, scalability via AWS infrastructure, and freedom from Elastic's license encumbrances for hosted instances. This service launch emphasized ease of migration for users, with options to run either legacy 2.0-licensed versions or the new OpenSearch fork under unified management.

Technical Foundation

Core Architecture and Components

OpenSearch employs a distributed architecture centered on for its indexing and search capabilities, enabling efficient handling of large-scale data through inverted indexes that map terms to documents. At the foundational level, data is organized into indexes, which are subdivided into primary —each functioning as an independent Lucene index—for parallel processing and distribution across nodes. , created by default as one copy per primary shard, provide redundancy for and enhance query performance by distributing read loads. This sharding and replication mechanism supports horizontal scalability, allowing clusters to expand by adding nodes without introducing single points of failure when configured with multiple nodes for quorum-based decision-making. The system operates within clusters, which are collections of interconnected nodes that collectively manage ingestion, storage, and retrieval. Node types include nodes, responsible for storing , performing indexing, and executing searches; nodes, which orchestrate cluster-wide operations such as allocation and node health monitoring; and ingest nodes, dedicated to preprocessing documents via pipelines before indexing to offload compute-intensive tasks from nodes. In production setups, dedicating three nodes across zones ensures resilience against node failures, as decisions require a . nodes are provisioned with sufficient RAM and storage to handle loads, typically balancing replicas across zones to mitigate zone-level outages. Interactions with the architecture occur primarily through a RESTful API over HTTP, facilitating real-time document ingestion, full-text searches with relevance scoring (using algorithms like BM25), and aggregations for on distributed . Queries are broadcast to relevant , with results aggregated at coordinating nodes to maintain consistency and efficiency. This design inherently supports near-real-time updates, as ingested documents become searchable shortly after indexing, while the absence of centralized bottlenecks—achieved via decentralized shard management—enables robust scaling for petabyte-scale datasets.

Key Features and Capabilities

OpenSearch supports vector search capabilities, enabling the storage and querying of vector embeddings alongside traditional data to facilitate and AI-driven applications, such as similarity matching via approximate nearest neighbor algorithms like k-NN. This integration allows for model deployment directly within search workflows, supporting tasks like neural search and without external dependencies. Additionally, it incorporates anomaly detection powered by the Random Cut Forest algorithm, which processes time-series data in near real-time to identify outliers and deviations, applicable to monitoring and . The suite includes functionalities for handling logs, metrics, and traces, unifying these signals into a single platform for root-cause analysis and performance monitoring, with tools to transform unstructured log data and visualize distributed traces across services. This setup supports ingestion from diverse sources via pipelines like Data Prepper, enabling efficient querying and alerting without additional licensing costs. Licensed under the Apache 2.0 terms, OpenSearch ensures permissive use that promotes extensibility through community contributions and custom modifications, facilitating self-hosting on-premises or multi-cloud environments while avoiding vendor-specific lock-in or escalating fees associated with proprietary shifts in upstream projects. This licensing model underpins cost predictability, as organizations can scale deployments independently of commercial vendors, leveraging the distributed architecture for across nodes.

Ecosystem and Extensions

OpenSearch Dashboards

OpenSearch Dashboards serves as the primary web-based user interface for OpenSearch, forked from version 7.10.2 in April 2021 to align with the OpenSearch project's emphasis on open-source licensing and community-driven development. It enables users to query, visualize, and manage data stored in OpenSearch indices through interactive tools, facilitating data exploration without requiring direct interactions. Unlike the original Kibana, which has diverged under Elastic's proprietary licensing model, OpenSearch Dashboards maintains with OpenSearch clusters while evolving independently to support features tailored to distributed search and workloads. Core functionalities include the creation of customizable dashboards that aggregate visualizations such as line charts, bar graphs, pie charts, and geographic maps for representing time-series data, metrics, and spatial information. The Discover tool allows ad-hoc querying and filtering of raw data using OpenSearch Query Language (OSQL) or Dashboard Query Language (DQL), supporting real-time analysis of logs, application metrics, and other indexed datasets. Visual Editor provides drag-and-drop capabilities for building complex visualizations, including heatmaps and treemaps, directly from index patterns, with support for aggregations like histograms and percentiles to derive insights from large-scale datasets. Post-fork, OpenSearch Dashboards has incorporated enhancements specific to security integration, such as native support for the OpenSearch Security plugin, enabling , audit logging, and encrypted communications within the visualization layer. Custom plugin development has been expanded through a modular , allowing extensions for advanced observability, visualizations, and trace analytics without reliance on proprietary Elastic features. Recent updates, including workspaces introduced in OpenSearch 3.0 (released May 2025), enable multi-tenant dashboard management and isolated environments for collaborative data exploration, improving scalability for enterprise deployments. These developments ensure ongoing compatibility with OpenSearch indices while addressing gaps in the original fork, such as enhanced plugin extensibility for custom UI components.

Plugins, Security, and Integrations

OpenSearch features a plugin architecture that allows extension of its search and analytics capabilities through modular components installed via the opensearch-plugin command-line tool. Key plugins in the ecosystem include the Alerting plugin, which evaluates data streams from one or more indexes against user-defined conditions—such as thresholds or scripts—and triggers actions when met, supporting use cases like real-time monitoring of log volumes or error rates exceeding 5% within a 5-minute window. The SQL plugin enables querying of OpenSearch indexes using ANSI SQL syntax, translating queries to the native DSL via REST APIs, JDBC/ODBC drivers, or a dedicated CLI tool, with support for features like aggregations, joins, and pagination limits up to 200 rows by default. Complementing these, the Notifications plugin aggregates and routes alerts from Alerting and other plugins to channels including email, Slack, Microsoft Teams, custom webhooks, and Amazon Chime, configurable via a unified interface in OpenSearch Dashboards. The Security plugin, bundled and enabled by default in OpenSearch installations since the project's inception in April 2021, delivers enterprise-grade protections distinguishing it from forked predecessors where core security often requires paid licensing. It enforces fine-grained (RBAC) with over 30 predefined action groups for permissions on indices, clusters, and dashboards; supports backends like internal users, HTTP basic auth, JWT, SAML, and Connect; and integrates with LDAP or for directory-based user mapping, allowing synchronization of groups to roles via attributes like memberOf. Additional safeguards include transport-layer encryption with TLS (enabled by default for node-to-node communication), for REST APIs (configurable), IP filtering, and comprehensive logging that records events like failures or unauthorized queries to files or external systems. Multi-tenancy in OpenSearch Dashboards isolates user spaces for visualizations and indices, enabled by default but adjustable in configuration files. Integrations with AWS services enhance OpenSearch's deployment flexibility, particularly in managed environments like Amazon OpenSearch Service. Native support for enables zero-ETL querying of object storage data without ingestion, announced in June 2024, allowing direct analysis of petabyte-scale datasets via SQL or dashboards. integration processes data transformations serverlessly, while OpenSearch Ingestion pipelines—launched in 2023—stream data from sources like Amazon Kinesis or RDS into domains with managed buffering and fault tolerance, supporting protocols such as HTTP and . These connect with third-party tools via standard APIs, promoting hybrid setups where on-premises OpenSearch clusters federate with cloud resources for unified analytics, as demonstrated in integrations with Amazon CloudWatch for metric alerting on domain health metrics like CPU utilization exceeding 80%.

Controversies and Criticisms

License Dispute with Elastic

In January 2021, Elastic NV relicensed and from the 2.0 to the (SSPL) and Elastic License 2.0 (ELv2), effective with version 7.11 released on February 11, 2021. Elastic justified the change as a measure to curb "free-riding" by large cloud providers, particularly (AWS), which had built managed services like Amazon Elasticsearch Service atop the software without proportionally contributing to its development or sharing innovations with the community. Under SSPL, users offering the software as a hosted service must release the source code of their entire service stack, a requirement Elastic argued aligns with open development principles while safeguarding against extraction of value by hyperscalers for commercial gain. AWS and the OpenSearch project countered that SSPL and ELv2 fail to qualify as open source licenses under the Open Source Initiative (OSI) definition, as they impose restrictions on redistribution and use in service hosting that discriminate against specific fields of endeavor, such as cloud operations. The OSI explicitly rejected SSPL approval in January 2021, citing violations of the Open Source Definition's clauses on free redistribution and non-discriminatory use, rendering the software source-available but not permissively open for broad community modification and forking. In response, AWS forked Elasticsearch 7.10.2—the last Apache 2.0 release—on April 12, 2021, to launch OpenSearch, preserving the license's freedoms to enable vendor-neutral development, unrestricted service offerings, and collaborative contributions without proprietary encumbrances. The dispute bifurcated the ecosystem, with OpenSearch fostering a community-driven project under 2.0 that supports ongoing forks and integrations free from service-hosting clauses, while Elastic emphasized enterprise subscriptions and dual-licensing for revenue sustainability. This split, while fragmenting user bases and contributor pools, underscored tensions between copyleft-style protections and permissive licensing, with OpenSearch's model upholding redistribution liberties central to traditional ethos.

Performance and Feature Gap Claims

Elastic has published multiple benchmarks asserting superior performance for compared to OpenSearch. In August 2023, Elastic reported as 108% faster in term queries and 103% faster in composite terms aggregations, attributing gains to optimizations in query execution and data structures unavailable in the open-source . Similarly, a 2024 Elastic analysis claimed up to 12 times faster in vector search operations, requiring fewer computational resources due to enhancements in indexing and retrieval algorithms. These results, spanning 2023-2024 workloads, positioned as 40-140% faster overall while consuming less hardware, though conducted under Elastic-controlled conditions that prioritized their ecosystem. Independent evaluations have yielded mixed outcomes, challenging uniform superiority claims. A March 2025 benchmark by Trail of Bits, a cybersecurity firm, compared OpenSearch 2.17.1 against 8.15.4 using the OpenSearch Benchmark tool across realistic scenarios; it found OpenSearch faster in aggregate on core "Big 5" operations like ingestion and querying, though Elasticsearch edged out in specific latency-sensitive tasks. Such variances stem from divergent development trajectories: Elasticsearch incorporates closed-source vector and accelerations post-fork (from Elasticsearch 7.10 in 2021), creating initial parity gaps in OpenSearch for advanced , whereas OpenSearch emphasizes community-vetted scalability enhancements. OpenSearch demonstrates advantages in AWS-native environments, where tight integrations with services like and EC2 enable horizontal scaling with lower operational overhead than self-managed deployments. For instance, OpenSearch's plugin ecosystem and zero-cost licensing reduce total ownership costs, offsetting raw query speed deficits through extensibility in distributed, cloud-agnostic setups—benefits evident in benchmarks favoring multi-node resilience over single-query velocity. Early post-fork criticisms highlighted feature lags, such as delayed plugins until OpenSearch 2.x releases via community backports, but ongoing contributions have narrowed these through modular architecture rather than proprietary silos. These dynamics reflect causal trade-offs: Elastic's proprietary path accelerates niche optimizations at the expense of , while OpenSearch's open model prioritizes verifiable, reproducible gains in for broader ecosystems. In 2019, initiated a against (AWS) in the U.S. District Court for the Northern District of , accusing AWS of , , and unfair competition. Elastic specifically contended that AWS's "Amazon Elasticsearch Service" and "Open Distro for Elasticsearch" misused Elastic's registered "" , creating consumer confusion by implying official affiliation or endorsement, and that AWS falsely advertised the offerings as fully compatible with Elastic's software. The suit did not challenge the technical forking of code under Elasticsearch's then-Apache 2.0 license, which permitted such derivatives as a core open-source norm, but highlighted AWS's branding practices as diluting Elastic's mark and misleading users about compatibility and support. The dispute culminated in a , 2022, settlement where AWS agreed to remove "" from all service and project names, , and materials, and to add disclaimers affirming no relationship with Elastic. This resolution aligned with AWS's prior April 2021 rebranding of its managed service from "Amazon Service" to "Amazon OpenSearch Service," a move explicitly aimed at mitigating risks while maintaining continuity for users through in-place upgrades from 6.x and 7.x versions. No admission of liability occurred, and the agreement underscored AWS's position that its practices complied with open-source licensing, with community-driven OpenSearch emphasizing transparency via its Apache 2.0 terms. These actions, distinct from licensing debates, reveal corporate strategies to safeguard brand identity amid open-source forking, potentially complicating adoption by fostering ecosystem fragmentation through name changes and required clarifications. However, OpenSearch's permissive ensures unrestricted and modification, insulating technical development from constraints and enabling broad community contributions without branding dependencies.

Adoption and Reception

Commercial and Community Use Cases

OpenSearch finds extensive application in commercial environments as an alternative to proprietary licensing, particularly through AWS OpenSearch Service, which enables enterprises to perform log analytics on petabyte-scale datasets from sources like Amazon S3. Companies such as , Netscout, and deploy it for managing large datasets in full-text search and analytics, while integrates it for automated index and cluster management in payment processing workflows. In and application monitoring, it supports real-time clickstream analysis and , with one enterprise reporting a 26% reduction in infrastructure costs—saving over $175,000 annually—after migrating from using AWS instances. Security analytics and represent additional commercial strengths, where OpenSearch ingests and visualizes logs from multiple sources for and compliance monitoring, often integrated with AWS services like Fargate for centralized pipelines. However, operational challenges persist, including high management complexity for self-hosted clusters, which demand specialized expertise in shard allocation, stability tuning, and scaling to avoid indexing slowdowns or latency spikes—issues less mitigated without Elasticsearch's commercial support ecosystem. AWS-managed deployments alleviate some burdens via serverless ingestion but still require adherence to best practices like dedicated nodes to maintain stability under heavy loads. In community-driven projects, OpenSearch powers tools adhering to OpenTelemetry standards for correlating data, and its k-NN plugin enables vector search for AI applications like semantic retrieval augmented generation. These initiatives, hosted under the Apache 2.0 license, facilitate no-cost scaling for open-source stacks and hybrid search enhancements, though contributors note ongoing needs for improved testing and agentic AI feedback loops to match enterprise-grade reliability. The absence of licensing fees supports in these areas, but effective deployment often hinges on community-sourced plugins and manual optimizations, underscoring the trade-off between cost savings and the expertise required for production-grade operations.

Comparative Market Position

OpenSearch has seen increasing adoption in environments prioritizing open-source licensing and vendor neutrality, particularly following 's 2021 shift to the (SSPL) and Elastic License, which restricted certain cloud provider usages and prompted the fork. This licensing change causally drove organizations away from toward OpenSearch to avoid potential lock-in and licensing fees, with OpenSearch now boasting over 1,400 unique contributors and more than 350 active ones as of 2025, reflecting robust community momentum. In contrast, maintains stronger loyalty among enterprises valuing proprietary enhancements, supported by Elastic's venture-funded development model that enables faster iteration on advanced features like vector search optimizations. Performance benchmarks, often conducted by Elastic, indicate Elasticsearch outperforming OpenSearch by 40% to 140% in areas such as text querying, aggregations, and resource efficiency, attributing gaps to differences in optimization and funding scale. Independent analyses, including those scaling to large datasets, suggest OpenSearch remains viable for most production workloads, with recent releases like version 3.0 incorporating GPU acceleration that yields up to 9.3x indexing speedups in specific scenarios, mitigating some lags inherent to its decentralized . Critics note that OpenSearch's community-driven pace can trail Elasticsearch's proprietary advancements, yet this model fosters broader extensibility and cost control without restrictive terms. The OpenSearch fork represents a market correction to perceived anti-competitive licensing practices, enhancing diversity in the search engine landscape by sustaining 2.0-licensed alternatives that integrate seamlessly across multi-cloud setups and prevent fragmentation. This divergence has empirically boosted open-source options' viability, as evidenced by sustained growth in OpenSearch's ecosystem despite Elasticsearch's established base, underscoring how licensing influences adoption over raw feature parity alone.

Recent and Future Developments

Transition to Linux Foundation

In September 2024, (AWS) announced the transfer of the OpenSearch project's governance to the , formally establishing the OpenSearch Software Foundation as a dedicated, vendor-neutral entity hosted under the foundation's umbrella. This handover, revealed on September 16 at the Open Source Summit Europe, marked a strategic pivot from AWS-led stewardship—initiated when AWS forked in 2021—to independent, community-oriented management. The primary objectives included expanding the contributor base beyond AWS affiliates, ensuring neutral technical and financial governance, and adhering to established open-source best practices for long-term project sustainability. Proponents argued this would mitigate lingering rooted in OpenSearch's origins as a corporate , fostering greater trust and collaboration in areas like search, , , and vector databases. Following the transition, the project gained immediate enhancements in perceived neutrality, positioning it to potentially accelerate and contributions from diverse stakeholders previously deterred by vendor-centric perceptions. This shift aligned OpenSearch with the Linux Foundation's track record of supporting resilient, multi-vendor ecosystems, thereby addressing criticisms of centralized control while preserving rapid innovation.

Version Evolution and Roadmap

OpenSearch 1.0 achieved general availability on July 12, 2021, establishing a stable, production-ready foundation with comprehensive compatibility for Elasticsearch 7.10 APIs and plugins, prioritizing reliability for enterprise deployments. The 2.x series commenced with version 2.0 on May 26, 2022, incorporating Lucene 9.1 for indexing improvements, new algorithms via the ML Commons plugin, and initial vector search capabilities to enable semantic and hybrid querying. Later iterations, including 2.16 (August 7, 2024) and 2.17 (September 17, 2024), expanded these with support for binary vectors from ML models, enhanced inference scalability, and disk-optimized storage to reduce costs in vector-heavy workloads. Version 3.0, released on May 6, 2025, advanced and through Lucene 10 upgrades, refined vector engine efficiency for lower usage, and improved replication mechanisms, addressing demands from AI-driven applications. The OpenSearch roadmap for 2024–2025 centers on deepening AI integrations, such as advanced vector search for generative AI pipelines and streamlined ML model deployment, alongside optimizations for and cost efficiency in large-scale clusters. Future priorities include cross-cluster capabilities for distributed resilience and empirical validation via tools like OpenSearch Benchmark 2.0, which facilitates reproducible testing to ensure measurable advancements in throughput and latency. This community-governed approach contrasts with proprietary development by fostering transparent, contributor-led progress verifiable through public benchmarks and release cadences.

References

  1. https://opensearch.org/
  2. https://aws.amazon.com/what-is/opensearch/
  3. https://opensearch.org/faq/
  4. https://docs.opensearch.org/latest/about/
  5. https://opensearch.org/platform/opensearch-core/
  6. https://opensearch.org/platform/opensearch-dashboards/
  7. https://docs.opensearch.org/latest/getting-started/intro/
  8. https://opensearch.org/blog/opensearch-project-update-performance-progress-in-opensearch-3-0/
  9. https://thenewstack.io/opensearch-whats-next-for-the-search-and-analytics-suite/
  10. https://opensearch.org/announcements/opensearch-software-foundation-marks-1-year-anniversary-with-community-growth-agentic-ai-and-hybrid-search-enhancements/
  11. https://www.elastic.co/pricing/faq/licensing
  12. https://aws.amazon.com/blogs/opensource/stepping-up-for-a-truly-open-source-elasticsearch/
  13. https://skywalking.apache.org/blog/2021-01-17-elastic-change-license/
  14. https://aws.amazon.com/blogs/opensource/introducing-opensearch/
  15. https://aws.amazon.com/opensearch-service/faqs/
  16. https://aws.amazon.com/blogs/opensource/opensearch-1-0-launches/
  17. https://aws.amazon.com/blogs/aws/announcing-amazon-opensearch-service-which-supports-opensearch-10/
  18. https://docs.opensearch.org/latest/tuning-your-cluster/
  19. https://docs.opensearch.org/latest/api-reference/
  20. https://opensearch.org/platform/vector-search/
  21. https://docs.opensearch.org/latest/observing-your-data/ad/index/
  22. https://opensearch.org/platform/anomaly-detection/
  23. https://docs.opensearch.org/latest/observing-your-data/
  24. https://aws.amazon.com/opensearch-service/features/observability/
  25. https://opensearch.org/blog/opentelemetry-metrics-visualization/
  26. https://opensearch.org/about/
  27. https://forum.opensearch.org/t/esa-2025-06-is-relevant-to-opensearch-dashboards/23656
  28. https://docs.opensearch.org/latest/dashboards/
  29. https://docs.opensearch.org/latest/dashboards/visualize/viz-index/
  30. https://opensearch.org/blog/dashboards-usability-snapshot/
  31. https://github.com/opensearch-project/OpenSearch-Dashboards/issues/4298
  32. https://www.instaclustr.com/blog/opensearch-3-0-is-here-whats-new-and-shiny-in-this-major-release/
  33. https://opensearch.org/blog/feature-highlight-opensearch-dashboards-notebooks/
  34. https://docs.opensearch.org/latest/install-and-configure/plugins/
  35. https://docs.opensearch.org/latest/observing-your-data/alerting/index/
  36. https://docs.opensearch.org/latest/search-plugins/sql/index/
  37. https://docs.opensearch.org/latest/observing-your-data/notifications/index/
  38. https://docs.opensearch.org/latest/security/
  39. https://docs.opensearch.org/latest/security/configuration/best-practices/
  40. https://aws.amazon.com/opensearch-service/
  41. https://aws.amazon.com/blogs/big-data/modernize-your-data-observability-with-amazon-opensearch-service-zero-etl-integration-with-amazon-s3/
  42. https://docs.aws.amazon.com/opensearch-service/latest/developerguide/ingestion.html
  43. https://docs.aws.amazon.com/opensearch-service/latest/developerguide/integrations.html
  44. https://www.elastic.co/blog/licensing-change
  45. https://www.elastic.co/blog/why-license-change-aws
  46. https://opensource.org/blog/the-sspl-is-not-an-open-source-license
  47. https://www.chaossearch.io/blog/opensearch-vs-elasticsearch-comparison
  48. https://last9.io/blog/opensearch-vs-elasticsearch/
  49. https://www.elastic.co/blog/elasticsearch-opensearch-performance-gap
  50. https://www.elastic.co/search-labs/blog/elasticsearch-opensearch-vector-search-performance-comparison
  51. https://blog.trailofbits.com/2025/03/06/benchmarking-opensearch-and-elasticsearch/
  52. https://uptrace.dev/comparisons/opensearch-vs-elasticsearch
  53. https://www.tecracer.com/blog/opensearch-vs-elasticsearch-2024/
  54. https://www.netdata.cloud/academy/elasticsearch-vs-opensearch/
  55. https://www.bloomberg.com/news/articles/2022-02-16/elastic-settles-suit-with-amazon-cloud-unit-over-alleged-copying
  56. https://www.theregister.com/2022/02/17/elastic_amazon_trademark/
  57. https://www.elastic.co/blog/elastic-and-amazon-reach-agreement-on-trademark-infringement-lawsuit
  58. https://www.zdnet.com/article/aws-scrubs-elasticsearch-from-site-to-settle-trademark-dispute-with-elastic/
  59. https://www.computerweekly.com/news/252513588/Amazon-drops-Elasticsearch-name-from-cloud-portfolio-after-trademark-infringement-suit-concludes
  60. https://aws.amazon.com/blogs/big-data/petabyte-scale-log-analytics-with-amazon-s3-amazon-opensearch-service-and-amazon-opensearch-ingestion/
  61. https://eliatra.com/blog/OpenSearch-key-Usecases/
  62. https://developer.payments.jpmorgan.com/blog/guides/elastic-opensearch
  63. https://opensearch.org/case-studies/case-study-modernizing-enterprise-search-with-opensearch-aws-graviton-4-and-bonsai/
  64. https://www.cloudtech.com/resources/business-operations-centralized-log-analytics-case-study
  65. https://aws.amazon.com/opensearch-service/features/integration/
  66. https://www.chaossearch.io/blog/elasticsearch-opensearch-challenges
  67. https://docs.aws.amazon.com/opensearch-service/latest/developerguide/bp.html
  68. https://aws.amazon.com/blogs/big-data/enhance-stability-with-dedicated-cluster-manager-nodes-using-amazon-opensearch-service/
  69. https://opensearch.org/platform/observability/
  70. https://opensearch.org/community-projects/
  71. https://thenewstack.io/opensearch-3-2-delivers-hybrid-search-enhanced-observability-tools/
  72. https://aws.amazon.com/blogs/big-data/moving-to-managed-the-case-for-amazon-opensearch-service/
  73. https://www.infoworld.com/article/3971473/opensearch-in-2025-much-more-than-an-elasticsearch-fork.html
  74. https://pureinsights.com/blog/2025/elasticsearch-vs-opensearch-in-2025-what-the-fork/
  75. https://dattell.com/data-architecture-blog/opensearch-vs-elasticsearch-in-2025-whats-changed-and-what-hasnt/
  76. https://socket.dev/blog/developers-burned-by-elasticsearch-license-change-arent-going-back
  77. https://wz-it.com/en/blog/opensearch-vs-elasticsearch-vendor-lock-in/
  78. https://www.reddit.com/r/elasticsearch/comments/1i1035l/is_the_2023_elasticsearch_vs_opensearch_benchmark/
  79. https://www.linuxfoundation.org/press/linux-foundation-announces-opensearch-software-foundation-to-foster-open-collaboration-in-search-and-analytics
  80. https://aws.amazon.com/blogs/opensource/aws-welcomes-the-opensearch-foundation/
  81. https://techcrunch.com/2024/09/16/aws-brings-opensearch-under-the-linux-foundation-umbrella/
  82. https://thenewstack.io/aws-transfers-opensearch-to-the-linux-foundation/
  83. https://www.linuxfoundation.org/blog/how-the-opensearch-software-foundation-will-ensure-long-term-sustainability-of-the-opensearch-project
  84. https://www.forbes.com/sites/adrianbridgwater/2024/09/29/why-aws-gave-opensearch-to-the-linux-foundation/
  85. https://aws.amazon.com/blogs/big-data/amazon-opensearch-service-managed-and-community-driven/
  86. https://opensearch.org/blog/driving-community-contributions/
  87. https://opensearch.org/blog/opensearch-general-availability-announcement/
  88. https://opensearch.org/blog/opensearch-2-0-is-now-available/
  89. https://opensearch.org/blog/introducing-opensearch-2-16/
  90. https://opensearch.org/blog/introducing-opensearch-2-17/
  91. https://opensearch.org/announcements/opensearch-3-0-enhances-vector-database-performance/
  92. https://opensearch.org/blog/opensearch-project-roadmap-2024-2025/
  93. https://opensearch.org/blog/introducing-opensearch-benchmark-2-0/
  94. https://opensearch.org/blog/building-the-future-of-opensearch-together/
Add your contribution
Related Hubs
User Avatar
No comments yet.