Introduction

This article describes the ports to be allowed by the network firewall for the Engage service to function as intended. 

The communication is bi-directional, as such, the firewall must allow both outgoing traffic (requests to the server) and incoming traffic (most of the time represents the answers to the requests).

Given the client/server architecture in place, the client will initiate most of the communication with the server. This will make the Amino Engage services work behind most NAT networks, the network firewall only needs to make sure the traffic in some specific ports and from some IP addresses is allowed.

Prerequisites

This article assumes that you have an Engage account and the device is deployed in your local network behind a firewall.

Summary

Regions

Engage is a global service with multiple instances and depending on the region the clients are deployed, different instances are used. To confirm which region we are using, we can check the domain details under System > Manage Domains > [Your domain name] > Region(s).

If nothing is specified, the domain is using the default region, which is US. If EMEA is specified, then the domain is using the EMEA region.

Once the server region and the modules subscribed are confirmed, we can follow the matching requirements below:

• For EMEA
• For US

Amino EngageSM Engage IP Requirements - EMEA

SYSTEM and WEB UI

MANAGE

RESOLVE

OPTIMIZE

Amino EngageSM Engage IP Requirements - US

SYSTEM and WEB UI

MANAGE

RESOLVE

OPTIMIZE

References 

None