Network Configuration

For Lumi AI to effectively respond to requests in Chat or Boards, it requires access to the source system connections defined within each Knowledge Base. Depending on the mode/type of connection, different considerations apply.

Direct Connections

A direct connection is the simplest connection type, providing a means for communication directly between Lumi AI's servers and the target system. Each system has different requirements for connection properties (see Source System Integrations for more details).

A direct connection requires inbound and outbound internet communication between source and target, meaning systems must have a public IP and accept incoming TCP connections.

For added security, you can restrict access via IP Whitelisting (see below).

Data Gateway

A more advanced connection method, where the direct method is insufficient or not applicable, involves the use of Lumi AI's Data Gateway -- a lightweight application for mediating connections between a system in the your/client network and Lumi AI's backend.

This approach requires downloading, configuring, and running an instance of the Data Gateway somewhere on the network with internet access that can still communicate freely with the source system. To learn more see here Data Gateway.

Data Gateways require no inbound internet access, and strictly communicate via outbound-initiated communications to Lumi AI. IP whitelisting is generally not required, but can be applied without conflict.

Note that Data Gateways are only available for the Enterprise license tier.

IP Whitelisting

Lumi AI uses several IP addresses for traffic inbound and outbound globally.

These IP's are currently:

  • (Global) 15.197.73.100

  • (Global) 15.197.95.231

  • (US-East) 3.22.158.185

  • (US-East) 18.190.93.61

  • (US-East) 18.224.164.162

Our legacy IP's will remain active until Friday March 21, 2025. Until the migration date, both sets of new and legacy addresses should be whitelisted (if actively implemented with your organization's firewall rules). After the migration date the legacy IP addresses will no longer apply.

For reference, the legacy IP addresses are:

  • (Global) 15.197.227.237

  • (Global) 3.33.220.125

  • (US-East) 3.131.73.177

  • (US-East) 3.131.204.125

  • (US-East) 3.18.128.114

When whitelisting, all IP's should be whitelisted (not just regional or global).

Last updated

Was this helpful?