Skip to content

Commit ed311df

Browse files
kuniseneedugon
andauthored
Update deploy-manage/deploy/cloud-enterprise/enable-custom-endpoint-aliases.md
Co-authored-by: Edu González de la Herrán <[email protected]>
1 parent c778e17 commit ed311df

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

deploy-manage/deploy/cloud-enterprise/enable-custom-endpoint-aliases.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,9 +33,6 @@ After installing or upgrading to version 2.10 or later:
3333
* For Fleet, the certificate needs to allow for **\*.fleet.<your-domain>**
3434
* For Universal Profiling, the certificate needs to allow for **\*.profiling.<your-domain>** and **\*.symbols.<your-domain>**
3535

36-
::::{note}
37-
If you plan to deploy [Integration Servers](../../deploy/cloud-enterprise/manage-integrations-server.md), you must add two additional wildcard subdomains, `*.fleet.<your-domain>` and `*.apm.<your-domain>`, to the Subject Alternative Names (SANs) attached to the proxy wildcard certificate.
38-
::::
3936

4037
3. In the **Platform** menu, select **Settings**.
4138
4. 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.

0 commit comments

Comments
 (0)