From 5957bc3d0188dc1b0c023714962373dad4b83fa1 Mon Sep 17 00:00:00 2001 From: Brie Carranza <bcarranza@gitlab.com> Date: Mon, 8 Apr 2024 12:24:53 -0400 Subject: [PATCH] Clarify scope of IP allowlist --- doc/administration/dedicated/configure_instance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/administration/dedicated/configure_instance.md b/doc/administration/dedicated/configure_instance.md index a9befa0dd434c..7f207b70bdf77 100644 --- a/doc/administration/dedicated/configure_instance.md +++ b/doc/administration/dedicated/configure_instance.md @@ -144,7 +144,7 @@ GitLab Dedicated limits the number of reverse PrivateLink connections to 10. ### IP allowlist -GitLab Dedicated allows you to control which IP addresses can access your instance through an IP allowlist. Once the IP allowlist has been enabled, when an IP not on the allowlist tries to access your instance an `HTTP 403 Forbidden` response is returned. +GitLab Dedicated allows you to control which IP addresses can access your instance through an IP allowlist. Once the IP allowlist has been enabled, when an IP not on the allowlist tries to access your instance an `HTTP 403 Forbidden` response is returned. The IP allowlist is applied to incoming Web requests only and does not apply to incoming SSH requests. IP addresses that have been added to your IP allowlist can be viewed on the Configuration page in Switchboard. You can add or remove IP addresses from your allowlist with Switchboard or a support request. -- GitLab