0
votes

In a sharding configuration across multiple Azure-VMs (Linux), each with its own sub-domain (wildcard *.domain.com Azure dns-zone), the gateway must parses the SUB-DOMAIN-NAME.domain.com connect attempt and access a remote Azure Table-Storage (or any other REST endpoint) to determine which target Azure-VM to use for this. This Azure-VM determined will then be used for the remainder of the sticky-session (affinity cookie).

This should be possible via PowerShell configuration, but current limitations seem to exist as described here: https://serverfault.com/questions/881988/azure-application-gateway-limitations-wildcard-ssl-cert

https://feedback.azure.com/forums/217313-networking/suggestions/19527121-application-gateway-support-wildcard-hosts-in-lis

Any tips on support for this scenario within the Azure Application Gateway or do I need to look elsewhere?

Secondary question but also necessary for this scenario: access to an Azure-table-storage from the Azure Application Gateway PowerShell possible?

1

1 Answers

0
votes
  1. You cant have wildcard listener in an Azure Application Gateway, but you can have a generic listener, which will route all traffic to some endpoint, so your listeners can be something like this:

    • hostA.domain.com > host1
    • hostB.domain.com > host2
    • hostA.example.com > host3
    • hostB.example.com > host4 ...
    • everything that doesnt match the above hostnames goes to this last listener > hostx
  2. there is no Azure Application Gateway PowerShell, you just have Azure Application Gateway module in PowerShell, so you can use anything you can regularly use in PowerShell along with Azure Application Gateway cmdlets. Here's an example of how to query Azure Table storage in PowerShell.