Jitterbit allowlist (whitelist) information

Introduction

Depending on the Jitterbit products used by your organization and your organization's specific scenario, certain Jitterbit IP addresses and URLs must be allowed access to communicate with your organization's network (formerly known as whitelisting).

In many situations, no network or firewall configurations are necessary to communicate with these IP addresses and URLs. However, if your network is behind a firewall that blocks access to all traffic except for specified domains, URLs, or IP addresses, you must configure the network to be able to communicate with Harmony.

The allowlist information provided here is applicable in these scenarios:

• Inbound communication: To allow cloud agents or eiCloud to access internal resources that are behind a firewall within your network.
• Outbound communication: To restrict a private agent, private API gateway, or Design Studio installation that is behind a firewall within your network to communicate only with Jitterbit services that are absolutely necessary.

You may also need to allowlist additional IP addresses or URLs within your network if hosting private infrastructure or on-premises endpoints that a private agent, private API gateway, or Design Studio installation that is behind a firewall within your network must communicate with.

Review the information provided below to determine which Jitterbit IP addresses and URLs need to be allowlisted for the specific scenario within your organization. If any IP addresses or URLs provided below are changed in the future, Jitterbit will provide a notice to customers about the change.

Determine your region

The specific IP addresses or URLs that require allowlisting are determined by the Harmony region that hosts your organization. The region is tied to a Harmony organization rather than a specific user. A user can be part of multiple organizations, as long as the organizations are all in the same region.

When you go to the Harmony portal login URL https://login.jitterbit.com, you are automatically redirected to the Harmony region corresponding with your IP-based geolocation:

• NA: Geolocations in North America and South America are redirected to https://apps.na-east.jitterbit.com/identity/login.
• EMEA: Geolocations in Europe, the Middle East, and Africa are redirected to https://apps.emea-west.jitterbit.com/identity/login.
• APAC: Geolocations in Asia-Pacific, including Australia, are redirected to https://apps.apac-southeast.jitterbit.com/identity/login.

When accessing an organization through the Harmony portal, the region can be inferred from the URL. That is, a URL containing apps.na is hosted in the NA region, apps.emea in the EMEA region, and apps.apac in the APAC region.

Inbound communication

You must allow these IP addresses for communication inbound to your network behind a firewall from cloud agents or eiCloud.

Allow cloud agents to access internal resources

If you use cloud agents and need to be able to access endpoints within your network (such as an on-premises database or a SQL database at Azure), you must allowlist these IP addresses for your region within your firewall:

Allow eiCloud to access internal resources

If you use Jitterbit eBridge Connections eiCloud and need to be able to access internal resources that are behind a firewall within your network, you must allowlist these IP addresses for your region within your firewall:

Outbound communication

You must allow these URLs to restrict the outgoing communication from a private agent, private API gateway, or Design Studio installation that is behind a firewall within your network to communicate only with Jitterbit services that are absolutely necessary. These URLs/IPs for your region must be allowlisted if you restrict outbound traffic on port 443 on your firewall.

NA region

EMEA region

APAC region