Your Elastic deployment stores data as documents within Elasticsearch indices. However, some Enterprise Search tools rely on additional features provided by the following index abstractions:

The following sections cover how to create and manage these various data stores:

Elasticsearch indicesedit

Elasticsearch stores and retrieves documents from indices (singular: index).

For Enterprise Search use cases, use the Search indices UI to create Elasticsearch indices (see Create index). You must use this interface to create indices for the web crawler and connectors, but you can also use this UI to create indices you will manage on your own.

Indices created through this UI are optimized for search use cases in the following ways:

The names of indices created through this UI always begin with search-.

Create indexedit

Within Kibana, navigate to Search → Content → Elasticsearch indices, and choose Create new index.

Select an ingestion method and provide any other information required to create the index.

This operation requires access to Kibana and the create_index or manage indices privilege.

App Search enginesedit

An App Search engine is an index abstraction that enables various App Search features, such as those used for searching, optimizing results, and gaining insights about your search experience.

Although it is possible to create an engine and index at the same time, the preferred solution is to first create an Elasticsearch index and then create an engine from that index. This solution enables the tools for search, results, and insights linked above (those that operate on engines and indices).

To manage documents and ingestion, use tools that operate directly on indices. Document management tools within App Search are read-only for engines created from indices.

See the App Search document, Elasticsearch index engines, to learn about the App Search features and field types that are supported by engines created from Elasticsearch indices.

Create engine (from index)edit

See the App Search document, Create Elasticsearch index engines, to create an App Search engine containing documents from an existing Elasticsearch index.

Example use case: You have ingested documents into an Elasticsearch index directly and now you want to build a search experience for it.

Example use case: You have a Workplace Search content source and want to use the App Search search API to query the content.

Create engine from content sourceedit

To create an App Search engine from a Workplace Search content source:

Example use case: You’ve ingested content using a Workplace Search connector. You want to build a search experience for this content with relevance tuning features in App Search.

Example use case: You want to build a search experience that searches content in Workplace Search content sources and App Search engines. Create an App Search engine and then combine multiple engines using a meta engine for a unified search experience.

Access engine indexedit

When creating a new App Search engine, you should first create an Elasticsearch index. In this case, you will know which index is used for the engine’s documents.

However, you may have existing App Search engines, where you did not create the index first. You can still access the Elasticsearch indices that contain the documents for these engines.

To find the index follow these steps in the Kibana UI:

Use the tools of your choice to manage and search the index’s documents.

Example use case: You created an App Search engine from an Elasticsearch index, but you still want to be able to access the index directly.

Example use case: You are an App Search user, but your requirements have outgrown the out-of-the-box capabilities of App Search. You want to leverage the full power of Elasticsearch to build more customized search experiences.

App Search meta enginesedit

A meta engine is an App Search feature that allows searching over multiple engines, combining their results.

Create meta engine (from engines)edit

Refer to the App Search documentation to create and manage meta engines.

Example use case: Your organization might have multiple content sources, each with different search settings and read/write permissions, but you also need a company-wide search experience with distinct curations or relevance tunings.

Example use case: You’ve ingested content into Elasticsearch indices using the Elastic web crawler. You’ve also ingested content into various Workplace Search content sources. You want to create a unified search experience across all this content by creating engines and a meta engine.

Workplace Search content sourcesedit

Workplace Search connectors sync to content sources. Content sources are similar to App Search engines, but they are a separate abstraction used by Workplace Search.

However, the following solutions allow you to access the documents of a content source outside of Workplace Search:

Access content source indexedit

You can directly access the Elasticsearch index that contains the documents for a Workplace Search content source. To find the index follow these steps in the Kibana UI:

Use the tools of your choice to manage and search the index’s documents.

Example use case: You want to create an engine from a content source. Accessing the underlying Elasticsearch index is a required intermediate step.

Example use case: You want to use Elastic index tools to work with the documents in a content source.