Virtual machines (VMs) 4 – Compute

Deploying a VM in the AWS environment involves similar steps as in Azure. The following steps highlight the process to deploy a VM in AWS, along with corresponding AWS CLI examples:

1. Sign in to the AWS console: Go to the AWS Management Console (https://aws.amazon.com/console/) and sign in with your AWS account.
2. Choose a region: Select the AWS region where you want to deploy your VM. Each region has its own availability zones, which are distinct data centers within the region.
3. Create a virtual private cloud (VPC): A VPC is a virtual network that allows you to isolate and control networking resources for your AWS resources. Create a new VPC or use an existing one.
   An example in AWS CLI is as follows:

aws ec2 create-vpc –cidr-block 10.0.0.0/16

4. Create a subnet within the VPC: Create a subnet where your VM will reside. Each subnet is associated with a specific availability zone.
   An example in AWS CLI is as follows:

aws ec2 create-subnet –vpc-id –cidr-block 10.0.1.0/24 –availability-zone us-east-1a

5. Choose the VM image: Select the Amazon Machine Image (AMI) that corresponds to the operating system and software you want to run on the VM.
   An example in AWS CLI (listing available AMIs) is as follows:

aws ec2 describe-images –owners amazon –query “Images[?Architecture==’x86_64′ && VirtualizationType==’hvm’ && RootDeviceType==’ebs’]”

6. Create the VM: Specify the instance type (hardware configuration), IAM role (if required for specific permissions), security groups (firewall settings), and other details.
   An example in AWS CLI is as follows:

aws ec2 run-instances –image-id –count 1 –instance-type t2.micro –key-name MyKeyPair –security-group-ids –subnet-id –associate-public-ip-address

7. Allocate a public IP (optional): By default, an EC2 instance in a public subnet will get a public IP. However, for instances in private subnets, you may need to assign an Elastic IP (EIP) and associate it with your instance.
   An example in AWS CLI is as follows:

aws ec2 allocate-address
aws ec2 associate-address –instance-id –public-ip

8. Open ports (optional): Configure security group rules to allow incoming traffic to specific ports, similar to NSG rules in Azure.
   An example in AWS CLI (allowing SSH traffic on port 22) is as follows:

aws ec2 authorize-security-group-ingress –group-id –protocol tcp –port 22 –cidr 0.0.0.0/0

9. Connect to the VM: Once the VM is deployed, connect to it using SSH for Linux instances or RDP for Windows instances. Use the public IP or EIP associated with the instance.
   That’s it! Now you have a VM running in the AWS environment. Again, remember to manage your resources efficiently, and stop or terminate instances when not in use to control costs.