---
title: "OpenSearch | Skills We Assign For | Azendo"
description: "OpenSearch for search and log analytics — licensing, AWS integration, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/opensearch/"
---

[Skills](https://azendo.co/skills/) Data stores and query 

# OpenSearch.

OpenSearch is an open-source search and analytics engine forked from Elasticsearch, maintained under the Apache 2.0 licence with its own vector search, security and alerting features.

## Where OpenSearch fits on a long engagement.

The fork happened over licensing, and for many organisations that is the entire decision. Apache 2.0 removes the commercial restrictions that came with Elasticsearch's licence change, which matters most to anyone embedding search in a product they sell.

The two have diverged since. Feature parity is no longer safe to assume, plugin ecosystems differ, and client libraries are not interchangeable. Choosing on the basis of a comparison from several years ago is how teams end up surprised by a missing capability.

## What an assigned team does with OpenSearch.

Log analytics is the most common deployment and the one where cost discipline matters most. Index lifecycle management moving old indices to cheaper storage and deleting them on schedule is the difference between a proportionate bill and a large one.

Configuring that properly is platform work, scoped alongside [devops managed services](https://azendo.co/services/cloud-and-devops/) rather than left to whoever set up the cluster.

## What we use OpenSearch for.

* Search without licence restrictions Apache 2.0 terms where search is embedded in a product being sold.
* Log retention managed by policy Lifecycle rules moving and expiring indices, which is the main cost lever.
* Feature parity verified Capabilities checked against current versions rather than assumed from the fork point.

## How OpenSearch capacity is assigned.

OpenSearch work is assigned inside platform or AI capacity depending on whether the constraint is operating the cluster or the relevance of what it returns.

## Roles we assign OpenSearch for

* [NLP Engineer AI engineering](https://azendo.co/services/ai-engineering/nlp-engineer/)

## Service lines it sits in

* [AI engineering](https://azendo.co/services/ai-engineering/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in data stores and query

* [SQL — skill we assign for](https://azendo.co/skills/sql/)
* [PostgreSQL — skill we assign for](https://azendo.co/skills/postgresql/)
* [MySQL — skill we assign for](https://azendo.co/skills/mysql/)
* [MongoDB — skill we assign for](https://azendo.co/skills/mongodb/)
* [Snowflake — skill we assign for](https://azendo.co/skills/snowflake/)
* [BigQuery — skill we assign for](https://azendo.co/skills/bigquery/)
* [Redis — skill we assign for](https://azendo.co/skills/redis/)
* [Prisma — skill we assign for](https://azendo.co/skills/prisma/)

## Tell us what your roadmap needs OpenSearch for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)