From e1d2529e3a5e7e7cc7d851862c1ccf8f2ed21d9b Mon Sep 17 00:00:00 2001 From: Peter Dyson Date: Fri, 9 May 2025 14:04:13 +1000 Subject: [PATCH] use standardized url for this common KB article --- deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md b/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md index d8fd289153..aac5bfa176 100644 --- a/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md +++ b/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md @@ -115,7 +115,7 @@ If your ECE installation is still using the default, auto-generated certificates If the license version is not 4 or higher, you must request an updated license from [Elastic Support](/troubleshoot/index.md#contact-us). Once you receive your new license, make sure {{ece}} is upgraded to at least version 2.5.0, and then upload the new license in the Settings page under the Platform menu. -In versions from 2.6 to 2.10 included, some or all platform certificates are generated with a 398-day expiration. Installations that ran on these versions, even temporarily, must have their certificates rotated manually before expiry. For details, check our [KB article](https://support.elastic.co/knowledge/ECE-Certificate-Rotation). +In versions from 2.6 to 2.10 included, some or all platform certificates are generated with a 398-day expiration. Installations that ran on these versions, even temporarily, must have their certificates rotated manually before expiry. For details, check our [KB article](https://ela.st/ece-certificate-rotation). ## Perform the upgrade [ece-upgrade-steps]