Azure design for external facing website

New Contributor


I have a requirement to migrate an containerized external facing website to Azure from AWS , how to define a landing zone for this requirement, I have read through azure documentation completely which says to start small or go for enterprise level landing zone but I'm not seeing an example architecture that suits my requirement, does anyone have any reference architecture on how an external facing web application can be deployed to containers in azure ?

1 Reply
This is how I would do it:

* 1 Subscription
* 1 Resource Group for Networking
* 1 Resource Group for Azure Management (Log Analytics, Diagnostic Storage account)
* 1 Resource Group for Backup
* 1 Resource Group for your Website/AKS/Container on WebApp + Database and App Gateway with Web Application Firewall (ie everything that has the same lifecycle).
Optional: 1 Resource Group for your external website dev/test.
* Enable Security Center