Hello Community,
We have a client who uses Amazon Connect as their contact center solution. The agents also have Netskope agents installed. According to our monitoring system, about 3.5% of calls are considered to have Poor Audio, and we are investigating possible causes.
When we checked the Netskope Steering exceptions, we currently have some steering exceptions configured, however, the one I’m concerned about is regarding the STUN (Media) UDP 3478 traffic.
According to the Amazon documentation (see Set up your network to use the Connect Customer Contact Control Panel (CCP) - Amazon Connect Customer), we need the following FQDN allowed:
TurnNlb-*.elb.region.amazonaws.com
When we check our steering profile configuration, this is the FQDN exception is configured:
*.amazonaws.com
From what I have been told, and by what I read in the Netskope documentation for Steering Profile Exceptions, it states:
“Wildcard domains (e.g., *.example.com) include the root domain and all subdomains.”
However, in the examples given in the article, it only shows one sub-domain level, and I’m curious if second, or third, or fourth, etc. are included.
So, for our steering profile, does “*.amazonaws.com” cover “TurnNlb-*.elb.region.amazonaws.com”?
Or should we be putting something more precise like “*.elb.region.amazonaws.com”?
Thanks,
John
