08 ‐ Order of steps to create a VM - SanjeevOCI/Study GitHub Wiki

Here is the order to create a VM in AWS, Azure, OCI, and GCP, along with the prerequisites for each:

1. AWS (EC2 Instance)

Order:

  1. VPC: Create a Virtual Private Cloud (VPC).
  2. Subnet: Create a subnet within the VPC.
  3. Security Group: Define inbound/outbound rules for the VM.
  4. Key Pair: Generate a key pair for SSH access.
  5. Route Table: Ensure a route to the Internet Gateway (if public access is needed).
  6. Elastic IP (Optional): Allocate if a static public IP is required.

Prerequisites:

  • AMI (Amazon Machine Image) for the OS.
  • Instance type (e.g., t2.micro).
  • IAM role (if needed for permissions).

2. Azure (Virtual Machine)

Order:

  1. Resource Group: Create a resource group to organize resources.
  2. VNet: Create a Virtual Network (VNet).
  3. Subnet: Create a subnet within the VNet.
  4. NSG: Configure a Network Security Group (NSG) for traffic rules.
  5. Public IP (Optional): Assign if public access is required.
  6. Storage Account (Optional): For custom images or data disks.

Prerequisites:

  • OS image (from Azure Marketplace or custom).
  • VM size (e.g., Standard_B2s).
  • SSH key or username/password for access.

3. OCI (Compute Instance)

Order:

  1. VCN: Create a Virtual Cloud Network (VCN).
  2. Subnet: Create a subnet within the VCN.
  3. Security List/NSG: Define traffic rules for the subnet or instance.
  4. Route Table: Ensure a route to the Internet Gateway (if public access is needed).
  5. Public IP (Optional): Assign if public access is required.

Prerequisites:

  • Custom or Oracle-provided image.
  • Shape (e.g., VM.Standard.E2.1).
  • SSH key for access.

4. GCP (Compute Engine)

Order:

  1. VPC: Use the default VPC or create a custom one.
  2. Subnet: Use the default subnet or create a custom one.
  3. Firewall Rules: Define rules for inbound/outbound traffic.
  4. Static IP (Optional): Reserve if a static public IP is required.

Prerequisites:

  • OS image (from GCP Marketplace or custom).
  • Machine type (e.g., e2-micro).
  • SSH key for access.

Summary of Things to Be Ready

Cloud Networking (VPC/Subnet) Security (Firewall/NSG) Access (Key Pair/SSH) Other (Public IP, Image, etc.)
AWS VPC, Subnet Security Group Key Pair AMI, Elastic IP (optional)
Azure VNet, Subnet NSG SSH Key/Password Resource Group, Public IP
OCI VCN, Subnet Security List/NSG SSH Key Public IP (optional)
GCP VPC, Subnet Firewall Rules SSH Key Static IP (optional)

This ensures all required components are ready before creating a VM in each cloud provider.