2 Answers
- Newest
- Most votes
- Most comments
1
Hi,
This happens very probably because the Execution role of your EC2 instance where you access the other AWS services doesn't have the proper permissions to access those AWS services.
To understand EC2 execution role, please, have a look at:
- https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html
- https://repost.aws/knowledge-center/assign-iam-role-ec2-instance
- https://www.youtube.com/watch?v=2m4_AdKbSY4
Best,
Didier
0
Well I fixed it by launching another instance but this time assigning an IPv4 for it. I really don't know if this is the problem but, it's the only thing that I did different (I was using only IPv6 since it's free). Thank you guys for your help!!
answered 2 years ago
Relevant content
asked 3 years ago
- AWS OFFICIALUpdated 5 years ago

Thank you! I tried to follow the steps on the YouTube video, really well made btw, but my issue persists! I even tried to create a new EC2 instance and do exactly what the person does on the video but, no deal! I managed to capture a screenshot with both, the command "aws iam list-users" before and after I attached the IAM role to the EC2, still getting a "Connect timeout on endpoint", gonna share the screenshot on the question