-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Cloud Client IP Restrictions Docs #62478
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
c0c029a
4b87adb
5e8b98e
ac5aa31
e57f8de
08c69cf
7748096
2d5cf83
7bccfc2
88d2f2a
f5decf4
01f9e7c
b21daa4
d5d74e3
1084c76
67625fd
798472e
7e23a40
728af92
00201d1
3b9d2ee
fbeed47
e948f70
6985985
c10c661
6139727
1a2002f
f90a676
ed796a6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,60 @@ | ||
| --- | ||
| title: Cloud Client IP Restrictions | ||
| description: Restrict access to your cloud cluster with a configurable allowlist. | ||
| tags: | ||
| - faq | ||
| - platform-wide | ||
| --- | ||
|
|
||
| **Client IP Restrictions** restrict access to your Teleport Cloud cluster, allowing traffic only from the specified network ranges (CIDR blocks). | ||
|
|
||
| ## How to enable | ||
| This feature is only available to Teleport Cloud customers and is opt-in only. Please contact your account executive or [customer support](https://goteleport.com/support/) to enable client IP restrictions for your tenant. | ||
|
|
||
| ## Adding CIDR blocks to the IP Allowlist | ||
|
|
||
| Log in to your Teleport Cloud account. Open the user dropdown menu on the top right of the navigation bar, and select "Help & Support," then scroll down until you see the IP Allowlist section. | ||
|
logand22 marked this conversation as resolved.
|
||
| If you do not see the IP Allowlist section, then it has yet to be enabled for your account. Please refer to [how to enable](#how-to-enable). | ||
|
|
||
| Once you add a CIDR, it will take effect in 5-20 minutes and will terminate existing connections. Changes to the allowlist are recorded in the audit log. | ||
|
|
||
| Managing allow rules is governed by Teleport’s existing RBAC system. | ||
| The preset `editor` role has permissions to read and write the allowlist. | ||
|
|
||
| You can also create custom roles granting access via the `client_ip_restriction` | ||
| resource. | ||
|
|
||
| ```yaml | ||
| allow: | ||
| - resources: [ client_ip_restriction ] | ||
| verbs: | ||
| # list is required to view the allowlist | ||
| - list | ||
| # create and update are required to modify the allowlist | ||
| - create | ||
| - update | ||
| ``` | ||
|
|
||
| ## Limitations | ||
|
|
||
| ### Misconfiguration | ||
| Misconfiguration can block all access to your cluster. Make sure to include your current network before saving changes. | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I can almost guarantee someone will lock themselves out. Do we have anything on the roadmap to address this footgun? Most systems with a feature like this will prevent you from blocking your own IP (or at least warn you first).
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We have an internal issue tracking additional improvements. https://github.com/gravitational/cloud/issues/15181 Unsure of the priority at this time. |
||
|
|
||
| ### Third-party service ranges | ||
| Teleport does not auto-add third-party service ranges. You must add allow rules for any third party service that needs to access your Teleport cluster (CI/CD systems, Identity Providers, etc.) | ||
|
|
||
| ### Network security | ||
| The allowlist applies to Teleport Cloud access; it does not replace your organization’s network/firewall policies. | ||
|
|
||
| ### Sync time | ||
| The Client IP Restriction allowlist may take up to 20 minutes before it is fully synced. | ||
|
|
||
| ## FAQ | ||
|
|
||
| ### How many CIDRs can you configure? | ||
|
|
||
| By default, up to 256 CIDR blocks can be configured. Please contact your account executive or customer support to increase the limit. | ||
|
|
||
| ### Do you support a denylist? | ||
|
|
||
| Teleport Cloud client IP restrictions do not currently support a denylist. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a cloud tag?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not that I know of.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could start one. We only just started the tags late last quarter, so the current set isn't exhaustive.