-1

I'm looking to leverage Azure deployment slots for a production Web App (with Azure SQL DB).

I also use a Fortiweb WAF-as-a-Service for production app.

If I use deployment slots, will I need a separate Fortiweb WAF-as-a-Service instance to point to new name of "ProductionApp/Staging"?

I suspect I would need DNS entries as well for new Staging name, along with a separate WAF to have the client successfully connect to staging deployment slot.

Any comments, pointers or other would be most welcomed.

Regards, Paul

neuro
  • 14,948
  • 3
  • 36
  • 59
PDorenberg
  • 1
  • Some additional findings on my side re: some constraints or shortcomings that won't work me are as follows, deployment slots can't swap custom client domain, associated ssl cert or scale settings. Additionally, as I would want to ensure that no changes were made to the database with a deployment of new code, a separate database would be required. Based on this info, deployment slots don't address my use case. I'll look to provision separate smaller instance, smaller db, separate cert and custom domain for the client. Cheers – PDorenberg May 09 '22 at 21:38

1 Answers1

2

Thank you to @PDorenberg for your question, and the subsequent solution that you provided in your comment.

For the sake of the community, I'm posting your comment as an answer, as it will benefit many others who are facing the same issue and are searching for a solution. Also, I've adding some points that I feel should be included and considered in the answer.

Deployment slots can’t swap custom client domain, associated private TLS/SSL certificates and scale settings as these settings are directly related to virtual network and private endpoints and these are ultimately related to the IP address space and DNS records created for them which are unique for every instance of resource that is routable, mappable and can be found over the internet through public IP addresses

Also, do keep in mind that only app settings, connection strings, language framework versions, web sockets, HTTP version, and platform bitness can be swapped between a deployment slot and a production slot. Please see the documentation for all the information regarding the deployment slot configuration and swapping.

Please also take note that you won’t need the Fortiweb WAF-as-a-service instance when pointing to the production slot of the app for a deployment that is already deployed in the staging slot of the App Service. But if the App Service instances are different for different apps in production, then you surely would need the Fortiweb WAF-as-a-service to route the traffic accordingly to each App Service instance separately.

Jeremy Caney
  • 7,102
  • 69
  • 48
  • 77
Kartik Bhiwapurkar
  • 4,550
  • 2
  • 4
  • 9