Amazon Machine Images (AMIs) in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the AMI ID when launching an EC2 instance.

AWS

aws ec2 run-instances --image-id [1] --count 1 --instance-type t2.micro

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

Akey-name

Bami-0abcdef1234567890

Csecurity-group

Dinstance-type

Attempts:

3 left

💡 Hint

Common Mistakes

Using instance type or security group instead of AMI ID.

Leaving the AMI ID blank.

The --image-id option requires the AMI ID, which identifies the Amazon Machine Image to use for the instance.

2fill in blank

medium

Complete the code to create a new AMI from an existing EC2 instance.

AWS

aws ec2 create-image --instance-id [1] --name "MyServerBackup"

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

Ai-1234567890abcdef0

Bami-0abcdef1234567890

Ct2.micro

DMyServerBackup

Attempts:

3 left

💡 Hint

Common Mistakes

Using an AMI ID instead of an instance ID.

Using the AMI name as the instance ID.

The --instance-id option requires the ID of the EC2 instance you want to create an AMI from.

3fill in blank

hard

Fix the error in the command to deregister an AMI by filling the blank with the correct option.

AWS

aws ec2 deregister-image --image-id [1]

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

AMyServerBackup

Bi-1234567890abcdef0

Cami-0abcdef1234567890

Dt2.micro

Attempts:

3 left

💡 Hint

Common Mistakes

Using the instance ID instead of the AMI ID.

Using the AMI name or instance type instead of the AMI ID.

The deregister-image command requires the AMI ID, which starts with 'ami-'. Using an instance ID or other values will cause an error.

4fill in blank

hard

Fill both blanks to create an AMI with a description and no reboot option.

AWS

aws ec2 create-image --instance-id [1] --name "BackupImage" --description [2] --no-reboot

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

Ai-0a1b2c3d4e5f6g7h8

B"Backup of server before update"

C"MyServerBackup"

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using AMI ID instead of instance ID for --instance-id.

Not quoting the description string.

The --instance-id requires the instance ID, and --description needs a string describing the AMI. The --no-reboot flag prevents reboot during image creation.

5fill in blank

hard

Fill all three blanks to launch an EC2 instance with a specific AMI, instance type, and key pair.

AWS

aws ec2 run-instances --image-id [1] --instance-type [2] --key-name [3] --count 1

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

Aami-0a1b2c3d4e5f6g7h8

Bt3.medium

CMyKeyPair

Di-1234567890abcdef0

Attempts:

3 left

💡 Hint

Common Mistakes

Using instance ID instead of AMI ID for --image-id.

Using AMI ID instead of instance type for --instance-type.

Using instance ID instead of key pair name for --key-name.

The --image-id specifies the AMI, --instance-type sets the size of the instance, and --key-name provides the SSH key pair for access.

Practice

1. What is the main purpose of an Amazon Machine Image (AMI)?

easy

A. To monitor server performance

B. To store user data in the cloud

C. To save a server setup so it can be reused later

D. To manage network traffic

Solution

1. Step 1: Understand what an AMI represents

   An AMI is a snapshot of a server's setup including its software and settings.

2. Step 2: Identify the main use of AMIs

   AMIs allow you to reuse this saved setup to launch new servers quickly.

3. Final Answer:

   To save a server setup so it can be reused later -> Option C

4. Quick Check:

   AMI = reusable server setup [OK]

Hint: AMI saves server setup for reuse [OK]

Common Mistakes:

• Confusing AMI with data storage
• Thinking AMI monitors performance
• Assuming AMI manages network

2. Which AWS CLI command correctly creates an AMI from a running instance with ID i-1234567890abcdef0?

easy

A. aws ec2 start-image --instance i-1234567890abcdef0 --name MyServerImage

B. aws ec2 launch-image --instance-id i-1234567890abcdef0 --name MyServerImage

C. aws ec2 make-ami --id i-1234567890abcdef0 --image-name MyServerImage

D. aws ec2 create-image --instance-id i-1234567890abcdef0 --name MyServerImage

Solution

1. Step 1: Identify the correct AWS CLI command for creating an AMI

   The correct command is aws ec2 create-image with the instance ID and a name.

2. Step 2: Match the command syntax with the options

   aws ec2 create-image --instance-id i-1234567890abcdef0 --name MyServerImage uses the correct command and parameters.

3. Final Answer:

   aws ec2 create-image --instance-id i-1234567890abcdef0 --name MyServerImage -> Option D

4. Quick Check:

   create-image + instance-id = create AMI [OK]

Hint: Use 'create-image' with instance ID to make AMI [OK]

Common Mistakes:

• Using wrong command like start-image or launch-image
• Mixing up parameter names
• Omitting instance ID

3. You run this AWS CLI command:
aws ec2 create-image --instance-id i-0abc123def456 --name TestImage
What will be the immediate result?

medium

A. An AMI creation request is started; image becomes available after processing

B. The instance is stopped and then an AMI is created

C. A new AMI is created and available instantly

D. The command fails because instance ID is invalid

Solution

1. Step 1: Understand the behavior of create-image command

   The command starts the AMI creation process but the image is not instantly ready.

2. Step 2: Identify the correct immediate result

   The AMI creation runs in background; the image becomes available after some time.

3. Final Answer:

   An AMI creation request is started; image becomes available after processing -> Option A

4. Quick Check:

   AMI creation is asynchronous [OK]

Hint: AMI creation takes time; not instant [OK]

Common Mistakes:

• Assuming AMI is ready immediately
• Thinking instance stops automatically
• Believing command fails without error

4. You tried to create an AMI with this command:
aws ec2 create-image --instance i-0abc123def456 --name MyImage
But it failed. What is the error?

medium

A. Instance ID format is incorrect

B. Missing required parameter --instance-id

C. AMI name is invalid

D. You cannot create AMI from a running instance

Solution

1. Step 1: Check the command parameters

   The command uses --instance instead of the required --instance-id parameter.

2. Step 2: Identify the cause of failure

   The AWS CLI expects --instance-id to specify the instance; missing this causes failure.

3. Final Answer:

   Missing required parameter --instance-id -> Option B

4. Quick Check:

   Use --instance-id to specify instance [OK]

Hint: Use --instance-id, not --instance [OK]

Common Mistakes:

• Using wrong parameter name
• Assuming instance ID format error
• Thinking AMI can't be made from running instance

5. You want to launch multiple identical servers quickly using an AMI. Which steps should you follow?

hard

A. Create an AMI from a configured instance, then launch new instances using that AMI

B. Launch new instances, then manually configure each one separately

C. Create snapshots of volumes, then attach them to new instances

D. Use AWS Lambda to copy instance settings to new servers

Solution

1. Step 1: Understand how to reuse server setups

   Creating an AMI from a configured instance saves its setup for reuse.

2. Step 2: Use the AMI to launch new instances

   Launching new servers from the AMI ensures they have the same software and settings quickly.

3. Final Answer:

   Create an AMI from a configured instance, then launch new instances using that AMI -> Option A

4. Quick Check:

   AMI enables fast identical server launches [OK]

Hint: Create AMI first, then launch servers from it [OK]

Common Mistakes:

• Configuring each server manually
• Using snapshots instead of AMIs for full setup
• Thinking AWS Lambda copies server setups