Below are the list of Data360 DQ+ Ports which need to be open for communication.
The AWS installation creates all the required security groups and ports for all the communication between components. A list of the ports used are below.
Ports available in inbound firewall
These are ports used from outside the DQ+ subnets into the subnets:
22 – EC2 Compute Instances
443 & 8080 – Application Load Balancer & Beanstalk
5432 – Aurora Postgres
5439 – Redshift Databases
8443, 8998 – EMR
Port available within the cluster subnets
All TCP traffic is open between the subnets.
Enterprise (on-prem) Edition
|AppServer to ComputeDB||22,5433,5450||Except port 22, other ports just need to be open for internal communication within Cluster.|
|ComputeDB to ComputeDB||22,4803||Except port 22, other ports just need to be open for internal communication within Cluster.|
|AppServer to AppServer / Load Balancer||22,7800-7810,8080,80/443||Ports "22,80/443" need to be open for communication outside the cluster. Rest of them just need to be open for internal communication.|
|AppServer to ApplicationDB||22,5432||5432 need to be open for internal cluster communication. And Port 22 need to be open for outside comm. so users can connect to the VM directly.|
* Load Balancer (Apache mod_cluster)
* AppServer (Tomcat)
* ApplicationDB (Postgres Database)
* ComputeDB (Vertica Database)