CNE AWS Ready: Using Elasticsearch

Cloud Native Experience environments provision OpenSearch by default for search and analytics workloads.

You can configure the platform to use Elasticsearch instead.

Note

Cloud Native Experience environments provision OpenSearch domains by default.

Running Elasticsearch does not disable OpenSearch automatically. Both services can run in the same environment without conflicts.

Elasticsearch Requirements

Using Elasticsearch requires

• A valid Liferay license
• A container image that includes the Elasticsearch connector module
• Configuration changes that remove the default OpenSearch connection settings

Configure the Elasticsearch Operator

Cloud Native Experience deploys the Elastic Cloud on Kubernetes (ECK) operator to manage Elasticsearch clusters in Kubernetes.

You can customize the operator configuration in your infrastructure repository.

The configuration is defined in infrastructure-provider.yaml under the eck-operator property.

For example, this configuration increases the operator resource limits:

eck-operator:
   resources:
      limits:
         cpu: 1000m
         memory: 1Gi

For the full configuration options supported by the operator, see the Elastic documentation.

Configure Elasticsearch

1. Provision an Elasticsearch instance in your infrastructure.

2. Add the Elasticsearch connection properties to ElasticsearchConfiguration.config.

3. Mount the configuration file in the Liferay container using a custom volume mount.

4. Deploy a Liferay image that includes the Elasticsearch connector module.

For more information about configuring Elasticsearch with Liferay, see Connecting to Elasticsearch.