You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs(clickpipes): Add new regions and clarify IP whitelisting logic
This commit adds new ClickPipes deployment regions (`ap-south-1`, `ap-southeast-2`, `us-west-2`) and updates the static IP address list.
The documentation is restructured to clarify the IP whitelisting requirements based on the service's creation date:
- Services in the new regions created on or after June 24/25, 2025, should use the new region-specific IPs.
- Older services in these regions must continue using the `us-east-1` IPs.
- The fallback logic for other regions is also clarified.
The following are the static NAT IPs (separated by region) that ClickPipes uses to connect to your external services. Add your related instance region IPs to your IP allow list to allow traffic.
58
+
59
+
For services created in `ap-south-1`, `ap-southeast-2`, and `us-west-2`**on or after 24 Jun 2025**, ClickPipes will be deployed in the same region, and you should use the region-specific IPs from the table below. For services created in these regions **before** this date, please use the IPs for `us-east-1`.
60
+
61
+
For all other services, ClickPipes traffic will originate from a default region based on your service's location:
62
+
-**eu-central-1**: For all services in EU regions.
63
+
-**us-east-1**: For all services in `us-east-1`.
64
+
-**us-east-2**: For all other regions not explicitly listed.
ClickHouse Cloud provides sensible defaults for most of the use cases. However, if you need to adjust some ClickHouse settings for the ClickPipes destination tables, a dedicated role for ClickPipes is the most flexible solution.
0 commit comments