A flaw in Adobe's Network Endpoint list for secure networks

We need to have a secure network in order to comply with film studio's security requirements to work on their films.  We are trying to open holes in the firewall so that our editors can sign the Creative Cloud app for Syncing settings and such.

Exploring the net it seems since Adobe moved to AWS I guess this has been an issue.

An adobe support rep sent me this saying to whitelist this giant list for non-browser services:

https://helpx.adobe.com/in/enterprise/kb/network-endpoints.html

Which is helpful, but Adobe's engineering guys have overlooked a very key issue that a firewall cannot whitelist a wildcard FQDN (ie *.adobesc.com).  It needs specific FQDN’s to resolve to IPs. 

This will never work properly in it's current state and the solution that Adobe's support guys are trying to sell will always be a fail.  Assuming they don't want that.  Other studio IT guys seem to be complaining about this as well. 

Would love a work around Adobe?!