Aurora Community static IP addresses
A variety of Aurora Community integrations may require allowlisting IP addresses associated with requests to external resources or services.
Some example integrations include:
- API Event Subscriptions (webhooks)
- Certain types of SSO, like OAuth 2 or OpenID Connect
- Custom Freemarker components using the http.client context object
- Custom back-end integrations built by Professional Services
If your Community-related security architecture includes IP based allowlists, the following values can be used:
| AMER production | AMER stage |
| 34.218.217.104 | 35.167.51.70 |
| 34.208.76.195 | 35.155.246.43 |
| 35.155.246.68 | 52.41.143.85 |
| EMEA production | EMEA stage |
| 52.213.102.195 | 52.214.128.6 |
| 34.246.41.42 | 52.51.95.11 |
| 34.246.43.26 | 52.208.187.165 |
| APAC production | APAC stage |
| 54.206.152.214 | 3.105.80.217 |
| 52.65.188.98 | 3.105.88.113 |
| 13.239.46.46 | 13.55.41.72 |
Note: The listed IP addresses are associated only with outbound requests from Community and are not valid for inbound requests to the Community. Community IPs used with inbound requests are variable and change over time. Do not use these IPs as an element of any DNS record.
If you're unsure if your Community is hosted in the AMER, EMEA, or APAC region, contact Khoros Support.
Updated 4 days ago
Version 7.0