Skip to main content
To ensure seamless communication between your infrastructure and Stigg, enterprise environments with restrictive firewall rules may need to whitelist specific IP addresses and domains used by Stigg. This document consolidates all IPs and endpoints that may require whitelisting.

​
Production IP addresses

The following IP address is used across multiple services in the Stigg platform: 18.119.35.43. This IP address is used for production webhook event delivery, workflow executions and any backend traffic originating from the Stigg production environment.
This IP address may change. We will notify affected customers ahead of time in case of an update.

​
API endpoints

If you’re not routing traffic through a proxy, your firewall must allow outbound access to the following domains used by the Stigg SDKs and backend integrations: If you’re an enterprise customer using a firewall and want to avoid domain whitelisting, we recommend routing SDK traffic through your own backend proxy. For full instructions, see Routing frontend SDK requests through a proxy.

​
Frontend SDK proxying

If you’re proxying frontend SDK requests through your own infrastructure, no additional IPs need to be whitelisted except your own. The proxy server should be configured to forward:
  • /core → https://api.stigg.io
  • /edge → https://edge.api.stigg.io
Ensure you preserve all required headers:
  • X-API-KEY
  • X-API-VERSION
  • X-CUSTOMER-KEY

​
AWS SQS endpoints

Stigg Sidecar and Stigg Proxy may communicate with Amazon SQS as part of workflow execution and event delivery. If your environment enforces outbound firewall rules, you must whitelist the AWS SQS regional endpoints relevant to your deployment. For example, in us-west-2, the following domains should be allowed:
  • sqs.us-west-2.amazonaws.com
  • *.queue.amazonaws.com
AWS SQS does not guarantee static IPs. Always whitelist the domains, not the resolved IP address. Attempting to allowlist individual IPs (e.g., 3.239.232.80) will not work reliably, since these IPs are subject to change without notice.If you are operating in another AWS region, adjust the domain accordingly (e.g., sqs.eu-central-1.amazonaws.com). See AWS SQS Endpoints and Quotas for the full list of supported regional domains.