mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-17 11:18:16 +00:00
- Fix 381 files where branding script corrupted variable names (e.g. isHanzo KMSTemplate -> isKmsTemplate) - Rebrand from "Hanzo KMS" to just "KMS" for white-label support (allows Lux KMS, Hanzo KMS, etc. via configuration) - 856 files, purely string replacements, no logic changes
40 lines
1.4 KiB
Plaintext
40 lines
1.4 KiB
Plaintext
---
|
|
title: "Networking"
|
|
sidebarTitle: "Networking"
|
|
description: "Network configuration details for KMS Cloud"
|
|
---
|
|
|
|
When integrating your infrastructure with KMS Cloud, you may need to configure network access controls. This page provides the IP addresses that KMS uses to communicate with your services.
|
|
|
|
## KMS IP Addresses
|
|
|
|
KMS Cloud operates from multiple regions. If your infrastructure has strict network policies, you may need to allow traffic from KMS by adding the following IP addresses to your ingress rules. These are the IP addresses that KMS uses when making outbound requests to your services.
|
|
|
|
<Tabs>
|
|
<Tab title="US Region">
|
|
```
|
|
3.213.63.16
|
|
54.164.68.7
|
|
```
|
|
</Tab>
|
|
|
|
<Tab title="EU Region">
|
|
```
|
|
3.77.89.19
|
|
3.125.209.189
|
|
```
|
|
</Tab>
|
|
|
|
<Tab title="Dedicated Cloud">
|
|
For dedicated KMS deployments, please contact your account manager for the specific IP addresses used in your dedicated environment.
|
|
</Tab>
|
|
</Tabs>
|
|
|
|
<Warning>
|
|
These IP addresses are static and managed by KMS. Any changes will be communicated with 60-day advance notice.
|
|
</Warning>
|
|
|
|
## What These IP Addresses Are Used For
|
|
|
|
These IP addresses represent the source IPs you'll see when KMS Cloud makes connections to your infrastructure. All outbound traffic from KMS Cloud originates from these IP addresses, ensuring predictable source IP addresses for your firewall rules.
|