How to Deploy Spring on Platform.sh with Elasticsearch
Back to home
On this page
To activate Elasticsearch and then have it accessed by the Spring application already in Platform.sh, it is necessary to modify two files.
Note
This guide only covers the addition of a service configuration to an existing Spring project already configured to deploy on Platform.sh. Please see the deployment guide for more detailed instructions for setting up app containers and initial projects.
1. Add the Elasticsearch service
In your service configuration, include Elasticsearch with a valid supported version:
elasticsearch:
type: elasticsearch:8.5
disk: 256
2. Add the Elasticsearch relationship
In your app configuration, use the service name searchelastic
to grant the application access to Elasticsearch via a relationship:
relationships:
elasticsearch: "elasticsearch:elasticsearch"
3. Export connection credentials to the environment
Connection credentials for Elasticsearch, like any service, are exposed to the application container through the PLATFORM_RELATIONSHIPS
environment variable from the deploy hook onward. Since this variable is a base64 encoded JSON object of all of your project’s services, you’ll likely want a clean way to extract the information specific to Elasticsearch into it’s own environment variables that can be used by Spring. On Platform.sh, custom environment variables can be defined programmatically in a .environment
file using jq
to do just that:
export ES_HOST=$(echo $PLATFORM_RELATIONSHIPS | base64 --decode | jq -r ".essearch[0].host")
export ES_PORT=$(echo $PLATFORM_RELATIONSHIPS | base64 --decode | jq -r ".essearch[0].port")
export SPRING_ELASTICSEARCH_REST_URIS="http://${ES_HOST}:${ES_PORT}"
export JAVA_OPTS="-Xmx$(jq .info.limits.memory /run/config.json)m -XX:+ExitOnOutOfMemoryError"
Tip
For access to more credentials options, check Spring common application properties and binding from environment variables.
4. Connect to Elasticsearch
Commit that code and push. The Elasticsearch instance is ready to be connected from within the Spring application.