Red Hat Linux 3-Tier Solution on Azure
- Solution Overview
- Template Solution Architecture
- Licenses and Costs
- Deployment Steps
- Deployment Time
- Post Deployment Steps
This Azure Quick Start template deploys a 3 Tier Red Hat Solution on Azure.The Solution includes Web tier Servers, Application tier Servers and Database Tier Servers running Red Hat Enterprise Linux 7.3. Template follows Standard best practices for running a 3 tier Red Hat Linux IaaS workload on Azure. This template will deploy specified number of VMs in each tier as per requirement.
Template Solution Architecture
This template will deploy:
- Four storage accounts: 3 for storing VM's disks of each tier, 1 for storing diagnostics data.
- One Virtual Network with four subnets.
- 4 Network Security Group, one for each subnet.
- External Load Balancer to load balance Web Traffic(HTTP & HTTPS) to web servers.
- Internal Load Balancer to load balance traffic for app VM's.
- 2 Public IP’s, one for external Load balancer and other for Jump VM.
- 3 Virtual Machine Availability sets for Web Tier, Application Tier and Database tier.
- One Jump VM to faclitate ssh access to all other tier VMs.
- Multiple Red Hat Enterprise Linux VMs for each tier as per parameter value specified during deployment.
Licenses and Costs
The Red Hat Enterprise Linux 7.3 image used in this solution is the PAYG model and doesn't require the user to license it, it will be licensed automatically after the instance is launched first time. Use of this image carries a separate hourly charge that is in addition to Microsoft's Linux VM rates. Total price of the VM consists of the base Linux VM price plus RHEL VM image surcharge. Click here for pricing details.
Azure Subscription with specified payment method (Red Hat Enterprise Linux is a market place product and requires payment method to be specified in Azure Subscription)
Build your Red Hat 3-Tier IaaS environment on Azure in a two simple steps:
- Launch the Template deployment by clicking on Deploy to Azure button.
- Fill in all the required parameter values, Accept the terms and condition on click Purchase.
The deployment takes about 5 minutes to complete.
Post Deployment Steps
After successful deployment, this template will output the IP address and FQDN of both external load balancer and Jump VM. Make a note of these values.
- To access all VM's via SSH, you need to first ssh into jump VM using its public ip captured from template outputs, from jump VM you can ssh into other VMs through via private IP.
- Alternatively You can also get public IP of Jump VM from overview blade in VM Settings.
- Load balancer is configured for load balancing HTTP(Port 80) and HTTPS(Port 443) to distribute traffic to web servers.You can configure web servers and start accessing websites using Load Balancer.
For any support related questions, issues or customization requirements, please contact firstname.lastname@example.org
Tags: object, Microsoft.Storage/storageAccounts, Microsoft.Network/networkSecurityGroups, Microsoft.Network/publicIPAddresses, Microsoft.Network/virtualNetworks, Microsoft.Compute/availabilitySets, Microsoft.Network/loadBalancers, Microsoft.Network/networkInterfaces, Microsoft.Compute/virtualMachines