Instance metadata and user data in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to retrieve the instance ID from metadata.

AWS

curl http://169.254.169.254/latest/meta-data/[1]

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

Auser-data

Binstance-id

Cpublic-ipv4

Dsecurity-groups

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'user-data' instead of 'instance-id' to get instance ID.

The instance ID is accessed via the 'instance-id' path in the metadata service.

2fill in blank

medium

Complete the code to fetch the user data of an EC2 instance.

AWS

curl http://169.254.169.254/latest/[1]

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

Auser-data

Bhostname

Cami-id

Dinstance-id

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'instance-id' instead of 'user-data' to get user data.

User data is accessed via the 'user-data' path in the metadata service.

3fill in blank

hard

Fix the error in the command to get the public IPv4 address from metadata.

AWS

curl http://169.254.169.254/latest/meta-data/[1]

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

Apublic-ipv6

Blocal-ipv4

Cprivate-ipv4

Dpublic-ipv4

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'local-ipv4' or 'private-ipv4' which give internal IPs.

The public IPv4 address is accessed via the 'public-ipv4' path.

4fill in blank

hard

Fill both blanks to retrieve the security groups and the AMI ID from metadata.

AWS

curl http://169.254.169.254/latest/meta-data/[1] && curl http://169.254.169.254/latest/meta-data/[2]

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

Asecurity-groups

Binstance-type

Cami-id

Dpublic-hostname

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing 'instance-type' or 'public-hostname' instead of 'ami-id'.

'security-groups' returns the security groups attached to the instance, and 'ami-id' returns the AMI used to launch the instance.

5fill in blank

hard

Fill all three blanks to write a shell script that fetches instance ID, user data, and availability zone.

AWS

#!/bin/bash
INSTANCE_ID=$(curl http://169.254.169.254/latest/meta-data/[1])
USER_DATA=$(curl http://169.254.169.254/latest/[2])
AZ=$(curl http://169.254.169.254/latest/meta-data/[3])
echo "Instance ID: $INSTANCE_ID"
echo "User Data: $USER_DATA"
echo "Availability Zone: $AZ"

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

Ainstance-id

Buser-data

Cplacement/availability-zone

Dpublic-ipv4

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'public-ipv4' instead of availability zone path.

This script fetches the instance ID, user data, and availability zone from the metadata service using the correct paths.

Practice

1. What is the primary purpose of instance metadata in AWS EC2?

easy

A. To provide information about the instance to itself

B. To store user files permanently

C. To allow external users to access the instance

D. To manage billing information for the instance

Solution

1. Step 1: Understand instance metadata role

   Instance metadata is data about the instance that the instance can access itself, such as its ID, IP address, or region.

2. Step 2: Differentiate from other options

   It is not for storing user files, external access, or billing management.

3. Final Answer:

   To provide information about the instance to itself -> Option A

4. Quick Check:

   Instance metadata = instance self-info [OK]

Hint: Instance metadata is info the server knows about itself [OK]

Common Mistakes:

• Confusing metadata with user data
• Thinking metadata is for external access
• Assuming metadata stores user files

2. Which IP address is used inside an EC2 instance to access instance metadata?

easy

A. 127.0.0.1

B. 169.254.169.254

C. 192.168.0.1

D. 10.0.0.1

Solution

1. Step 1: Recall the special metadata IP

   A fixed IP address 169.254.169.254 is reserved for instance metadata access inside EC2 instances.

2. Step 2: Exclude other common IPs

   127.0.0.1 is localhost, 192.168.0.1 and 10.0.0.1 are private network IPs but not for metadata.

3. Final Answer:

   169.254.169.254 -> Option B

4. Quick Check:

   Metadata IP = 169.254.169.254 [OK]

Hint: Metadata IP always starts with 169.254 [OK]

Common Mistakes:

• Using localhost IP 127.0.0.1
• Confusing with private network IPs
• Trying public IP addresses

3. Given this user data script for an EC2 instance:

#!/bin/bash
echo "Hello World" > /home/ec2-user/hello.txt

What will happen when the instance starts?

medium

A. The file will be created but empty

B. The instance will fail to start due to syntax error

C. Nothing happens because user data is ignored

D. The file /home/ec2-user/hello.txt will contain 'Hello World'

Solution

1. Step 1: Understand user data script execution

   User data scripts run once at instance start and can create files or run commands.

2. Step 2: Analyze the script effect

   The script writes 'Hello World' into the file /home/ec2-user/hello.txt, so the file will contain that text.

3. Final Answer:

   The file /home/ec2-user/hello.txt will contain 'Hello World' -> Option D

4. Quick Check:

   User data script writes file content [OK]

Hint: User data runs at start and executes commands [OK]

Common Mistakes:

• Thinking user data runs multiple times
• Assuming syntax error in simple echo
• Believing user data is disabled by default

4. You try to access instance metadata from your EC2 instance using curl http://169.254.169.254/latest/meta-data/ but get no response. What is the most likely cause?

medium

A. Instance metadata service is disabled or blocked

B. The IP address is incorrect

C. User data script is missing

D. The instance is stopped

Solution

1. Step 1: Check IP correctness

   The IP 169.254.169.254 is correct for metadata service, so IP is not the issue.

2. Step 2: Consider service availability

   If no response, the metadata service might be disabled or blocked by firewall or instance settings.

3. Final Answer:

   Instance metadata service is disabled or blocked -> Option A

4. Quick Check:

   No metadata response = service disabled/blocked [OK]

Hint: No metadata response usually means service disabled [OK]

Common Mistakes:

• Assuming wrong IP address
• Confusing user data with metadata
• Not checking instance state

5. You want to automate installing software on an EC2 instance at launch using user data. Which of these is the best practice?

hard

A. Manually SSH into the instance after launch to install software

B. Store installation commands in instance metadata

C. Write a shell script in user data that installs software and runs on first boot

D. Use user data only to store instance tags

Solution

1. Step 1: Understand user data purpose

   User data is designed to run scripts automatically at instance launch to configure or install software.

2. Step 2: Evaluate options

   Manual SSH is not automated, metadata is read-only info, and tags are not stored in user data.

3. Final Answer:

   Write a shell script in user data that installs software and runs on first boot -> Option C

4. Quick Check:

   User data automates setup scripts [OK]

Hint: Use user data scripts to automate setup at launch [OK]

Common Mistakes:

• Trying to store commands in metadata
• Ignoring automation benefits
• Misusing user data for tags