We utilize Amazon Web Services and have an Elastic Load Balancer. We have a single host name registered in EPI Admin (e.g. - www.mydomain.com). This has forced us to use TCP health checks, because AWS simply checks by IP address (e.g. - https://1.1.1.1 instead of https://www.mydomain.com). We tried setting up wildcard (*) in IIS bindings, but the site does not respond still with anything but the proper FQDN.
Is there a way to use a wildcard (*) in EPI Server CMS so that any HTTP(S) request to the server returns the EPI Server site we have on these instances?
We utilize Amazon Web Services and have an Elastic Load Balancer. We have a single host name registered in EPI Admin (e.g. - www.mydomain.com). This has forced us to use TCP health checks, because AWS simply checks by IP address (e.g. - https://1.1.1.1 instead of https://www.mydomain.com). We tried setting up wildcard (*) in IIS bindings, but the site does not respond still with anything but the proper FQDN.
Is there a way to use a wildcard (*) in EPI Server CMS so that any HTTP(S) request to the server returns the EPI Server site we have on these instances?