Azure VM Creation
- Factors impacting Virtual machine creation
- VM Image
- Vm Size
- Zone/Region Selection
- Subnet
- Managed Disk
- Local Disk
- Cloud-init/User data
- In azure zone is selected by Virtual machine option and generally most vms get two types of disk
- Managed disk:
- This is created on a different physical server
- This is persistent/non-ephemeral
- local disk
- This is created on a same physical server
- This is temporary/ephemeral (data will be available as long as machine is running.)
- Managed disk:
- In AWS when we select instance type we are selecting
- cpu
- ram
- instance family (hardware)
- network speed
- optional local storage
-
In Azure when we select vm size
- cpu
- ram
- instance family (hardware)
- local disk (Size)
- Maximum number of managed disks

-
Azure free plan
- VM: 750 hours each of B1s, B2pts v2 (Arm-based), and B2ats v2 (AMD-based) burstable VMs
- Disk: 2 64 GB (P6) solid state drives SSD storage, plus 1 GB snapshot and 2 million I/O operations
Lets create a VM in Azure which install nginx.
- Azure Organization:
- Management Group
- Account
- Subscription
- Resource Group
- Resource

- Refer Here for quick start from Azure
- Create a Resource Group
-
Create a vm and ensure in the Advanced tab you select user data and enter the script to install nginx

- Lets login into linux instance and
Explore disks
- The local disks are generally mounted to /mnt

AWS also has an option for local storage – instance store
- Instance store is available only for certain instance types.
