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📝 Debug Q14 of 15

AWS - EC2 Fundamentals

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?

AInstance metadata service is disabled or blocked

BThe IP address is incorrect

CUser data script is missing

DThe instance is stopped

Step-by-Step Solution

Solution:

Step 1: Check IP correctness
The IP 169.254.169.254 is correct for metadata service, so IP is not the issue.
Step 2: Consider service availability
If no response, the metadata service might be disabled or blocked by firewall or instance settings.
Final Answer:
Instance metadata service is disabled or blocked -> Option A
Quick Check:
No metadata response = service disabled/blocked [OK]

Quick Trick: No metadata response usually means service disabled [OK]

Common Mistakes:

MISTAKES

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

Master "EC2 Fundamentals" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More AWS Quizzes

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?

Step 1: Check IP correctness

Step 2: Consider service availability

Final Answer:

Quick Check:

Want More Practice?