Launching an EC2 instance in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the Amazon Machine Image (AMI) ID when launching an EC2 instance.

AWS

ec2 = boto3.resource('ec2')
instance = ec2.create_instances(ImageId='[1]', MinCount=1, MaxCount=1, InstanceType='t2.micro')

Drag options to blanks, or click blank then click option'

Aami-0abcdef1234567890

Bkey-pair

Csecurity-group

Dinstance-type

Attempts:

3 left

💡 Hint

Common Mistakes

Using instance type or security group instead of AMI ID.

The ImageId parameter requires the AMI ID, which looks like ami-0abcdef1234567890. This tells AWS which image to use for the instance.

2fill in blank

medium

Complete the code to specify the instance type when launching an EC2 instance.

AWS

ec2 = boto3.resource('ec2')
instance = ec2.create_instances(ImageId='ami-0abcdef1234567890', MinCount=1, MaxCount=1, InstanceType='[1]')

Drag options to blanks, or click blank then click option'

Aami-0abcdef1234567890

Bsg-12345678

Ct2.micro

Dmy-key-pair

Attempts:

3 left

💡 Hint

Common Mistakes

Using AMI ID or security group ID instead of instance type.

The InstanceType parameter defines the size and power of the instance. t2.micro is a common small instance type.

3fill in blank

hard

Fix the error in the code by filling the correct parameter name for the key pair when launching an EC2 instance.

AWS

ec2 = boto3.resource('ec2')
instance = ec2.create_instances(ImageId='ami-0abcdef1234567890', MinCount=1, MaxCount=1, InstanceType='t2.micro', [1]='my-key-pair')

Drag options to blanks, or click blank then click option'

AKeyPair

BKeyName

CKey

DKeyId

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect parameter names like 'KeyPair' or 'Key'.

The correct parameter to specify the key pair name is KeyName. This allows you to connect to the instance securely.

4fill in blank

hard

Fill both blanks to add a security group and a tag to the EC2 instance.

AWS

ec2 = boto3.resource('ec2')
instance = ec2.create_instances(ImageId='ami-0abcdef1234567890', MinCount=1, MaxCount=1, InstanceType='t2.micro', SecurityGroupIds=['[1]'], TagSpecifications=[{'ResourceType': 'instance', 'Tags': [{'Key': 'Name', 'Value': '[2]'}]}])

Drag options to blanks, or click blank then click option'

Asg-12345678

BMyInstance

Cami-0abcdef1234567890

Dt2.micro

Attempts:

3 left

💡 Hint

Common Mistakes

Using AMI ID or instance type as security group.

Confusing tag key and value.

The SecurityGroupIds parameter expects a list of security group IDs like sg-12345678. The tag Name is set to a friendly name like MyInstance.

5fill in blank

hard

Fill all three blanks to create an EC2 instance with a specific subnet, assign a public IP, and add a tag.

AWS

ec2 = boto3.resource('ec2')
instance = ec2.create_instances(ImageId='ami-0abcdef1234567890', MinCount=1, MaxCount=1, InstanceType='t2.micro', NetworkInterfaces=[{'SubnetId': '[1]', 'DeviceIndex': 0, 'AssociatePublicIpAddress': [2]], TagSpecifications=[{'ResourceType': 'instance', 'Tags': [{'Key': 'Name', 'Value': '[3]'}]}])

Drag options to blanks, or click blank then click option'

Asubnet-1a2b3c4d

BTrue

CWebServer

DFalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect subnet ID format.

Using string 'True' instead of boolean True.

The SubnetId specifies the subnet like subnet-1a2b3c4d. AssociatePublicIpAddress is a boolean to assign a public IP, here True. The tag Name is set to WebServer.

Practice

1. What does launching an EC2 instance in AWS create?

easy

A. A storage bucket

B. A virtual server in the cloud

C. A database instance

D. A physical server in your office

Solution

1. Step 1: Understand EC2 purpose

   EC2 stands for Elastic Compute Cloud, which provides virtual servers.

2. Step 2: Identify what launching means

   Launching an EC2 instance means creating a virtual server in AWS cloud.

3. Final Answer:

   A virtual server in the cloud -> Option B

4. Quick Check:

   EC2 instance = virtual server [OK]

Hint: EC2 = virtual server, not physical hardware [OK]

Common Mistakes:

• Confusing EC2 with physical hardware
• Thinking EC2 creates storage or database
• Mixing EC2 with S3 storage

2. Which AWS CLI command is used to launch a new EC2 instance?

easy

A. aws ec2 run-instances

B. aws ec2 start-instance

C. aws ec2 create-instance

D. aws ec2 deploy-instance

Solution

1. Step 1: Recall AWS CLI commands for EC2

   The correct command to launch EC2 instances is 'run-instances'.

2. Step 2: Eliminate incorrect commands

   Commands like 'create-instance', 'start-instance', and 'deploy-instance' do not exist or are incorrect.

3. Final Answer:

   aws ec2 run-instances -> Option A

4. Quick Check:

   Launch EC2 = run-instances command [OK]

Hint: Remember 'run-instances' to start EC2 instances [OK]

Common Mistakes:

• Using 'create-instance' which is invalid
• Confusing 'start-instance' with launching
• Assuming 'deploy-instance' is a valid command

3. What will happen if you run this command?

aws ec2 run-instances --image-id ami-12345678 --count 1 --instance-type t2.micro --key-name MyKeyPair --security-groups MySecurityGroup

medium

A. Deletes the specified AMI image

B. Creates a new security group named MySecurityGroup

C. Launches one t2.micro EC2 instance with specified settings

D. Starts an existing stopped EC2 instance

Solution

1. Step 1: Analyze the command parameters

   The command uses 'run-instances' with image ID, count=1, instance type, key pair, and security group.

2. Step 2: Understand the command effect

   This command launches one new EC2 instance of type t2.micro with the given AMI and security settings.

3. Final Answer:

   Launches one t2.micro EC2 instance with specified settings -> Option C

4. Quick Check:

   run-instances with parameters = launch instance [OK]

Hint: run-instances with --count 1 launches one instance [OK]

Common Mistakes:

• Thinking it deletes or modifies AMI
• Confusing security group creation with usage
• Assuming it starts an existing instance

4. You run this command but get an error: InvalidKeyPair.NotFound. What is the likely cause?

aws ec2 run-instances --image-id ami-87654321 --count 1 --instance-type t3.small --key-name WrongKey --security-groups Default

medium

A. The key pair named 'WrongKey' does not exist in your AWS account

B. The AMI ID is invalid

C. The instance type t3.small is not supported

D. The security group 'Default' is missing

Solution

1. Step 1: Understand the error message

   'InvalidKeyPair.NotFound' means the specified key pair is not found in your AWS account.

2. Step 2: Match error to command parameters

   The key-name 'WrongKey' likely does not exist or is misspelled, causing the error.

3. Final Answer:

   The key pair named 'WrongKey' does not exist in your AWS account -> Option A

4. Quick Check:

   InvalidKeyPair error = missing key pair [OK]

Hint: Check key pair name spelling if InvalidKeyPair error occurs [OK]

Common Mistakes:

• Assuming AMI or instance type caused the error
• Thinking security group 'Default' is missing
• Ignoring key pair existence in the region

5. You want to launch 3 EC2 instances with the same settings but different subnet IDs for high availability. Which approach is best?

hard

A. Use aws ec2 create-subnet to create three subnets and launch one instance

B. Run one aws ec2 run-instances command with --count 3 and a single --subnet-id

C. Launch one instance and then clone it twice manually

D. Run three separate aws ec2 run-instances commands, each with a different --subnet-id

Solution

1. Step 1: Understand subnet and instance launch

   Each EC2 instance can be launched in only one subnet at a time.

2. Step 2: Plan for multiple subnets

   To launch instances in different subnets, run separate commands specifying each subnet ID.

3. Step 3: Evaluate options

   Run three separate aws ec2 run-instances commands, each with a different --subnet-id. This runs three commands with different subnet IDs, ensuring instances spread across subnets.

4. Final Answer:

   Run three separate aws ec2 run-instances commands, each with a different --subnet-id -> Option D

5. Quick Check:

   One subnet per instance, multiple commands for multiple subnets [OK]

Hint: One subnet per instance, use multiple commands for multiple subnets [OK]

Common Mistakes:

• Trying to launch multiple subnets in one command
• Assuming cloning instances copies subnet settings
• Confusing subnet creation with instance launch