Custom endpoint aliases allow users to replace the UUID for each application with a human readable string. Platform administrators must enable this feature to allow deployment managers to create and modify aliases for their deployments.
You need to update your proxy certificates to support this feature.
After installing or upgrading to version 2.10 or later:
- Login to the Cloud UI
Update your proxy certificate(s). In addition to currently configured domains, additional SAN entries must be configured for each application-specific subdomain:
If you are not using wildcard certificates, you need to repeat this process for each deployment to account for specific aliases.
- For Elasticsearch, the certificate needs to allow for *.es.<your-domain>
- For Kibana, the certificate needs to allow for *.kb.<your-domain>
- For APM, the certificate needs to allow for *.apm.<your-domain>
- For Enterprise Search or AppSearch, the certificate needs to allow for *.ent.<your-domain>
- For Fleet, the certificate needs to allow for *.fleet.<your-domain>
- In the Platform menu, select Settings.
- Under the Enable custom endpoint alias naming, toggle the setting to allow platform administrators and deployment managers to choose a simplified, unique URL for the endpoint.
If you do not perform these steps, application endpoints will behave as they did in versions before 2.10.
To learn about setting up custom endpoint aliases for your deployments, check Custom endpoint aliases.
Intro to Kibana
ELK for Logs & Metrics