Overview
Higher Logic Vanilla Cloud makes outbound connections from a small set of public egress addresses. Use this list when you need to allow traffic from Vanilla to your own systems, such as identity providers, webhooks, API integrations, or sites that restrict inbound connections by source.
Outbound traffic uses the egress address for the region that hosts your community. If you are not sure which region applies, allowlist every DNS record below, or contact Vanilla Support.
Allowlist the DNS records, not the IP addresses. These IP addresses can change without notice. Firewall, WAF, and allowlist rules should reference the DNS hostnames so they keep working when an address changes. Rules that reference only an IP address will stop matching after a change.
Production egress addresses
The IP addresses in this table are the current addresses for each DNS record. Treat them as a snapshot. The DNS records are the stable identifiers.
| Cloud | Region | DNS record | Current IP address |
|---|
| AWS | US West (us-west-2) | aws-prod-usw2b.egress.vanillaforums.net | 52.35.250.92 |
| AWS | Europe (eu-central-1) | aws-prod-euc1a.egress.vanillaforums.net | 3.67.123.222 |
| AWS | Canada (ca-central-1) | aws-prod-cac1d.egress.vanillaforums.net | 3.98.134.237 |
| Azure | Canada Central | azure-prod-cac1.egress.vanillaforums.net | 20.151.15.128 |
Allowlisting
- Prefer the DNS hostname in firewall, WAF, and allowlist rules.
- If a control only accepts IP addresses, use the current address in the table and plan to update it whenever the DNS record changes.
- Allowlist every production record above if your community's region is unknown, or if Vanilla may call your systems from more than one region.
Related