2 Answers
- Newest
- Most votes
- Most comments
0
The script is probably using the EC2 Instance Meta Data Service to find the region it is in. Was IMDS turned off or set to only support V2 of the IMDS?
0
For me, this was resolived by installing the rh-amazon-rhui-client rpm. Because I could not do anything with dnf (yum), I could not install it with "dnf install rh-amazon-rhui-client". I had to go to a working server, run "dnf download rh-amazon-rhui-client", which downloaded the file rh-amazon-rhui-client-4.0.14-1.el8.noarch.rpm. I copied that file to the broken server and ran "rpm -Uvh rh-amazon-rhui-client-4.0.14-1.el8.noarch.rpm" to install it. Then, when I ran "dnf update", it reconfigured itself and began working.
answered 8 months ago
Relevant content
- asked 4 months ago
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 5 months ago
It wasn't IMDS directly, but when I looked into what IMDS was, I realized that the host based firewall (I know it seems redundant but it's a requirement) was blocking access to 169.254.169.254 which IMDS uses. Thanks!