CPM installation may fail when the instance is fronted by an Elastic Load Balancer (ELB) or an Application Load Balancer (ALB)

CPM installation may fail when the instance is fronted by an Elastic Load Balancer (ELB) or an Application Load Balancer (ALB)

Background:
By default when creating a new AWS Elastic Load Balancer (ELB) or an Application Load Balancer (ALB) it has a default timeout of 60 seconds. During the CPM installation this timeout value can be exceeded and cause the CPM installation to fail. What this means is that after 60 seconds of "no activity" or no data flowing in the connection between the load-balancer and the backend instance, in this case, the N2WS appliance,the load-balancer will silently close the connection and cause the CPM installation to fail.
For more details on changing this idle timeout value see this link below.
https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-idle-timeout.html

If changing the ELB/ALB idle timeout value to 10 minutes does not allow the CPM installation to proceed successfully then the next step is to disable the ELB or ALB and run the installation again.