Dynamic IP addressing in Reltio cloud environments

Reltio's cloud architecture is built on highly dynamic infrastructure. Components such as load balancers and scaling services can change underlying IP addresses without notice as part of normal cloud operations.

Because cloud infrastructure is dynamic and uses load balancers:

• IP addresses behind load balancers change frequently.
• Static IP-based whitelisting is unreliable and difficult to maintain.
• Maintaining firewall rules based on specific IPs can result in unexpected connectivity failures.

In specific scenarios, Reltio allocates static public IP addresses for services hosted in Kubernetes clusters. In these cases, outbound traffic routes through Network Address Translation (NAT) gateways configured with static public IP addresses.

Examples of such scenarios include:

• Integrating with customer systems that require IP allowlisting for inbound or outbound traffic.
• Connecting to third-party APIs or partner platforms that restrict access to pre-approved source IP addresses.

• Meeting regulatory mandates that require fixed, traceable egress IP addresses for security auditing.

• Establishing secure site-to-site connectivity where static IPs are required for firewall configuration.

However, this applies only to specific services and environments. It cannot be generalized as a single, fixed list of IP addresses for all Reltio services.

Recommended security approach

The Reltio Security team strongly recommends that you whitelist Fully Qualified Domain Names (FQDNs) of Reltio service endpoints instead of IP addresses.

FQDN-based whitelisting is the preferred and supported method for securing inbound and outbound connectivity to Reltio.

Reference Links

Use the following links to obtain the latest IP ranges and related configuration details: