Outbound IP addresses

When Bloomreach connects to external systems—such as file storage, databases, SFTP servers, or webhook endpoints—those connections come from a fixed set of IP addresses registered exclusively to Bloomreach. You can use these IPs to restrict access to your systems so that only traffic from Bloomreach is accepted.

📘

Note

Outbound IP addresses are the IPs Bloomreach uses when it connects to your systems. These are different from the IPs your systems use to connect to Bloomreach.

Where to find your outbound IPs

Your outbound IPs are available in:

From either screen you can view the full list of outbound IPs for your instance, copy individual IPs, or download the complete list.

🚧

Important

Outbound IPs differ between instances and regions. Always use the IPs shown in your own settings screen—don't rely on IPs shared by other customers or listed in community resources.

Optional API monitoring

Your security team can optionally integrate with the Outbound IPs API and check the list regularly. This isn’t required for using outbound IP allowlisting.

Bloomreach aims to keep outbound IP changes infrequent. However, regularly checking the API can make any future additions or rotations easier to manage, helping your team keep firewall rules up to date without manual checks. The API response includes a freshness timestamp so automated systems can detect if and when the list has changed.

Which integrations use outbound IPs

Bloomreach uses outbound IPs when connecting to external systems for imports and exports. Configure your firewall or access rules to allowlist these IPs for the following integrations:

IntegrationImportsExportsNotes
Amazon S3Required only if your S3 bucket policy restricts access by IP
Azure Storage (Blob / ADLS Gen 2)Required only if your Azure storage account uses network rules
DatabricksRequired if your Databricks IP access list restricts by IP
Google BigQueryNot supported. BQ uses GCP access controls. See BQ documentation for guidance.
Google Cloud StorageNot supported. GCS uses GCP access controls. See GCS documentation for guidance.
MSSQL / Azure SQLRequired if your database firewall restricts by IP
MySQLRequired if your database firewall restricts by IP
PostgreSQL / RedshiftRequired if your database firewall restricts by IP
SFTPRequired if your SFTP server restricts access by IP
SnowflakeRequired if your Snowflake network policy restricts by IP
SSH tunnelsRequired if your SSH server restricts inbound connections by IP
URLRequired if your URL endpoint restricts inbound traffic by IP.
WebhooksRequired if your webhook endpoint restricts inbound traffic by IP. Enable Use static IPs on the webhook configuration screen.

How to use your outbound IPs

  1. Go to Project settings > Security or Workspace settings > Security.

  2. Copy individual IPs or download the complete list.

  3. Add the IPs to your system's allowlist, firewall rules, or network access controls.

For integration-specific guidance:

IntegrationHow to allowlist
Amazon S3Add the IPs to your S3 bucket policy using the aws:SourceIp condition.
Azure StorageAdd the IPs to your storage account's network rules.
Databases (MySQL, PostgreSQL, Redshift, MSSQL, Azure SQL)Open your database firewall to allow inbound connections on the database port from the Bloomreach IPs.
DatabricksAdd the IPs to your Databricks IP access list.
Google Cloud StorageIP-based allowlisting is not supported for GCS. Use GCP access controls. See GCS documentation for guidance.
SFTPOpen your SFTP server firewall to Bloomreach IPs on the port defined in your integration settings.
SnowflakeAdd the IPs to your Snowflake network policy.
SSH tunnelsOpen your SSH server firewall to allow inbound connections from Bloomreach IPs on port 22 (or your configured SSH port).
WebhooksConfigure your endpoint's firewall or reverse proxy to accept inbound requests from Bloomreach IPs. Enable Use static IPs on the webhook configuration screen.

Related pages



Did this page help you?

© Bloomreach, Inc. All rights reserved.