By using the Azure Private Endpoint for your Azure SignalR, it allows clients on a virtual network (VNet) to securely access data over a Private Link. As next step, let’s learn how to use the Azure Application Gateway for your Azure SignalR to manage the real-time traffic.
Azure Application Gateway is a web traffic load balancer that enables you to manage traffic to your web applications. Using the Azure Application Gateway with Azure SignalR Service enables you to:
- Protect your applications from common web vulnerabilities.
- Get application-level load-balancing for your scalable and highly available applications.
- Setup end to end secure.
- Customize the domain name.
Let’s go through the key steps together and learn how to implement this reference solution:
- The Application Gateway helps you protect your applications and setup end to end secure.
- The client cannot access the Azure SignalR Service instance through public network, and all the traffic is managed through Application Gateway.
- The traffic between App Service and SignalR Service is also protected by Virtual Network.
- Create the Virtual Network VN1.
- There is a default subnet already created, and add 2 new subnets:
- Create the resource of Azure SignalR Service ASRS1.
- Go to the ASRS1 in the portal.
- Go to the Private endpoint connections blade, and create a new private endpoint PE1 with the VN1 and its default subnet. Learn more details about use private endpoint for Azure SignalR Service.
- Resource Type: Microsoft.SignalRService/SignalR
- Resource: ASRS1
- Integration with private DNS zone: Yes
- Subnet: default subnet in VN1
- Go to the network access control blade of ASRS1 and disable the all connections in public network.
- Create the Application Gateway AG1
- In the Basic, use the VN1 and gatewaySN to configure the virtual network.
- In the Frontends, create a new public address.
- In the Backends, create a new backend pool signalr for the SignalR Service resource. You need to use the host name of the SignalR Service resource as the Target.
- In the Configuration, add a new routing rule signalrrule to route the traffic to SignalR Service. You need to create a new HTTP setting.
- Protocol: HTTP (We use the HTTP frontend protocol on Application Gateway in this blog to simplify the demo and help you get started easier. But in reality, you may need to enable HTTPs and Customer Domain on it with production scenario.)
- Backend targets
- Target type: Backend pool
- Add new HTTP setting
- Backend protocol: HTTPs
- Use well known CA certificate: Yes
- Override with new host name: Yes
- Host name override: Pick host name from backend target.
- Review and create the AG1
Now, we already setup the Virtual Network, SignalR Service and Application Gateway. Let’s quick test whether the configuration is correct.
- Go to the network access control blade of ASRS1 and set public network to allow server connection only.
- Go to AG1, open health probe, change the health probe path to /api/v1/health
- Go to the Overview blade of AG1, and find out the Frontend public IP address
- Open http://frontend-public-IP-address, and it should return 403.
- Open http://frontend-public-IP-address/api/v1/health, and it should return 200.
- Go back to the network access control blade of ASRS1 and disable the server connection in public network.
Now, the traffic to Azure SignalR is already managed by the Application gateway. The customer could only use the public IP address or custom domain name to access the resource. In this blog, let’s use the chat application as an example, and start from running it locally.
- Clone the github repo https://github.com/aspnet/AzureSignalR-samples
- Go to the Keys blade of ASRS1 and get the connection string
- Go to samples/Chatroom and open the shell
- Set the connection string and run the application locally
dotnet restore dotnet user-secrets set Azure:SignalR:ConnectionString "<connection-string-of-ASR1>;ClientEndpoint=http://< frontend-public-IP-address-of-AG1>" dotnet run
- Open http://localhost:5000 and view network traces via explorer to see WebSocket connection is established through AG1
- Create a Web App WA1.
- Publish: Code
- Runtime stack: .NET Core 3.1
- Operation System: Windows
- Go to Networking blade and configure the VNET integration.
- Select VN1 and webapp subnet applicationSN
- Publish the Web App with CLI
- Publishe the application and its dependencies to a folder for deployment
dotnet publish -c Release
- Package the bin\Release\netcoreapp3.1\publish folder as app.zip.
- Perform deployment using the kudu zip push deployment.
az login az account set –subscription <your-subscription-name-used-to-create-WA1> az webapp deployment source config-zip -n WA1 -g <resource-group-of-WA1> --src app.zip
- Go to the Configuration blade of WA1, and add following application setting to set connection string and enable private DNS zone.
Azure__SignalR__ConnectionString=<connection-string-of-ASR1>;ClientEndpoint=http://< frontend-public-IP-address-of-AG1> WEBSITE_DNS_SERVER=220.127.116.11 WEBSITE_VNET_ROUTE_ALL=1
- Go to the TLS/SSL settings blade of WA1, and turn off the HTTPS Only. To Simplify the demo, we used the HTTP frontend protocol on Application Gateway. Therefore, we need to turn off this option to avoid changing the HTTP URL to HTTPs automatically.
- Go to the Overview blade and get the URL of WA1.
- Open the URL by replacing the https with http, and open network traces to see WebSocket connection is established through AG1.
Now, you are successful to build a real-time chatroom application with Azure SignalR Service and use Application Gateway to protect your applications and setup end to end secure.
If you are trying to build your own application with Azure SignalR and Application Gateway, you could also get more helpful resources from the Azure SignalR Service and Azure Application Gateway. We are looking forward your feedback and ideas to help us become better via Azure Feedback Forum! You could also go to Tech Community to learn more blogs about Azure SignalR Service.