Elasticsearch access control

Last updated: 9/3/2026

To prevent Elasticsearch from using non-secured access types (such as HTTP unencrypted protocol), you need to edit a configuration file in your Remote Engine Gen2 installation.

Procedure

Go to the Remote Engine Gen2 installation directory.
Open the default/docker-compose.yml file to edit it.
Find the following parameter in the service named livy and make sure its value is set to false.
```
livy:
	...
	environment:
		...
		CONNECTORS_ENABLE_NON_SECURED_ACCESS: "false"
```
It will prevent the Elasticsearch connector from accepting http:// protocol which is unencrypted.
In the same file, look for the same parameters in the services named previewrunner and component-server and change their values to false as well.
Save your changes and close the file.
Restart the engine to take these changes into account.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here