How amanm13/azure-stack works
• Resource Group Module – Acts as the container for all Azure resources and provides a logical grouping.
• Networking Module – Responsible for creating an Azure Virtual Network (VNet) with three subnets. This module lays down the foundation for your three tiers:
• Each subnet represents one tier of your application: the presentation/web tier, application tier, and data tier.
• Security Group Module – Configures network security groups (NSGs) that apply firewall rules and enforce the traffic policies:
• For example, one NSG rule allows public inbound traffic to the web tier while restricting direct inbound access to the database tier.
• Compute Module – Provisions virtual machines, network interfaces, and (if applicable) availability sets:
• One VM is designated for the web tier (exposed to the internet) and another for the application tier (which has controlled traffic from the web tier).
• Database Module – Creates the database server and the associated database:
• Notice the connection design where the application tier can communicate with the database, but not vice versa, matching the security criteria.
Flow and Dependencies
• Within the networking section, illustrate that the Virtual Network is divided into three subnets, and clearly indicate how each subnet connects to its respective module:
• The web VM (which accepts inbound traffic from the internet).
• The application VM (which interacts with both the web VM and the database).
• To represent the isolation implied by the security rules (e.g., the database not being accessible directly from the web tier).
Architectural Patterns and Principles
• Layered Three-Tier Architecture: Visually separate the presentation layer (web), business logic (application), and data management (database) to reflect the classic three-tier model.
• Infrastructure as Code (IaC): Include a note that these modules are connected via Terraform (using files like main.tf, vars.tf, and terraform.tfvars) that ensures repeatable and predictable deployments.