mirror of
https://github.com/andwati/zitadel.git
synced 2026-10-18 05:52:51 +00:00
8ccd5b206f
Changes: - **Search**: Replaced Inkeep with Fumadocs' native built-in search (createFromSource). Removed @inkeep/cxkit-react and custom search dialogs. - **Hydration Fix**: Removed markdown links from ### headings in egress.mdx (across all versions) to fix the <a inside a> DOM mismatch error. - **Console Fix**: Added the missing key prop to <VersionSelector/> in the layout to resolve the React list warning. --------- Co-authored-by: Florian Forster <[email protected]> Co-authored-by: Claude Fable 5.1 <[email protected]>
50 lines
2.4 KiB
Plaintext
50 lines
2.4 KiB
Plaintext
---
|
|
title: ZITADEL Cloud Egress IP Addresses
|
|
sidebar_label: Egress IPs
|
|
description: "The static egress IP addresses used by ZITADEL Cloud for secure outbound connections to your infrastructure."
|
|
---
|
|
|
|
When configuring your firewall or network security groups, you may need to allow traffic **from** ZITADEL Cloud to your internal infrastructure.
|
|
|
|
This page lists the static Egress (outgoing) IP addresses used by ZITADEL Cloud regions.
|
|
|
|
## When do I need this?
|
|
|
|
You need to allowlist these IP addresses if you use features where ZITADEL initiates a connection to your systems. This is commonly required for the following scenarios:
|
|
|
|
### Identity Providers & Federation
|
|
If you are federating an [external Identity Provider (IdP)](/guides/integrate/identity-providers/introduction) that sits behind a firewall:
|
|
* **LDAP / Active Directory:** When ZITADEL connects to your LDAP server (typically port `636` for LDAPS).
|
|
* **OIDC / OAuth:** When ZITADEL connects to your IdP for:
|
|
* **Discovery:** Fetching configuration from `/.well-known/openid-configuration`.
|
|
* **Token Exchange:** Exchanging the authorization code at the `token_endpoint`.
|
|
* **User Info:** Retrieving user details from the `userinfo_endpoint`.
|
|
* **Keys:** Fetching signing keys from the `jwks_uri`.
|
|
* **SAML:** If ZITADEL needs to fetch the `metadata.xml` or artifact resolution services from an internal SAML IdP.
|
|
|
|
### Notification Providers
|
|
For custom [Notification Providers](/guides/manage/customize/notification-providers):
|
|
* [**SMTP:**](/guides/manage/customize/notification-providers#smtp-providers) If you configured a custom SMTP sender pointing to your own mail server.
|
|
* [**Webhook / HTTP provider:**](/guides/manage/customize/notification-providers#webhook-http-provider) If you use a custom gateway for SMS or Emails.
|
|
|
|
### Custom Logic
|
|
* **[Actions V1](/concepts/features/actions)**
|
|
* **[Actions V2](/concepts/features/actions_v2)**
|
|
|
|
## IP Addresses by Region
|
|
|
|
We recommend allowing the IP address corresponding to the region where your ZITADEL instance is hosted.
|
|
|
|
| Region | Egress IP Address |
|
|
| :--- | :--- |
|
|
| **Switzerland** | `34.65.158.196` |
|
|
| **Europe** | `34.107.19.72` |
|
|
| **United States** | `34.69.146.246` |
|
|
| **Australia** | `34.87.243.23` |
|
|
|
|
<Callout type="info">
|
|
|
|
To find out which region your ZITADEL Cloud instance is running in, check the [ZITADEL Customer Portal](https://zitadel.com/admin/instances).
|
|
|
|
</Callout>
|