Connectivity problem

Hello there,

It is highly possible that the instances hosting the domains need Elastic IPs which allows the instances to have static ip addresses. About Elastic IPs, refer to reference [1].

Another way to solve this problem would be to involve entering the whitelist into the router’s configuration interface or editing the firewall rules on your computer.

Consider the following factors when implementing whitelisting on your Firewall:

1. Whitelist based on domain name rather than ip address if your firewall allows.
2. If the firewall does not support domain whitelisting but only supports ip whitelisting, consider having a static IP mapped to the domain.

If the domain is pointing to a resource such as an Application Load Balancer (ALB) or Classic Load Balancer (CLB), its IP address will keep changing due to scaling events.

• High traffic causes ALB/CLB to scale up adding more nodes hence more ips.

If the domain is pointing to the ALB consider:

 i. Network Load Balancer (NLB) infront of ALB, see reference [2].

 ii. AWS Global Accelerator (GA) infront of the ALB, see reference [3].

 iii. If it's CLB migrate to ALB or NLB ,see reference [4].

References:

[1] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html

[2] https://docs.aws.amazon.com/elasticloadbalancing/latest/network/create-network-load-balancer.html

[3] https://docs.aws.amazon.com/global-accelerator/latest/dg/about-accelerators.alb-accelerator.html

[4] https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/migrate-classic-load-balancer.html