Home » Cloud » [solved] how to fix the “In order to sign requests, 169.254.169.254 must be accessible or valid credentials must be set. Please ensure your proxy environment variables allow access to 169.254.169.254 (NO_PROXY) or that your credentials have a valid access key and secret key” error message

[solved] how to fix the “In order to sign requests, 169.254.169.254 must be accessible or valid credentials must be set. Please ensure your proxy environment variables allow access to 169.254.169.254 (NO_PROXY) or that your credentials have a valid access key and secret key” error message

This articles will walk you thru on resolving the AWS proxy address error message when service is not able to start and throwing out   the following error message “In order to sign requests, 169.254.169.254 must be accessible or valid credentials must be set. Please ensure your proxy environment variables allow access to 169.254.169.254 (NO_PROXY) or that your credentials have a valid access key and secret key” .This error is not unique to an OS type or version as it spans both a Windows Server 2012R2 Instance, and a Windows Server 2016 Instance

 

The 169.254.169.254 is the link-local address where you can access metadata for your instance [1]. Based on the information you provided us previously and the logs you provided in your most recent update, it appears that your instances are unable to reach the metadata service. I reviewed the Windows Firewall settings from the .cab file that you provided and see that you have the Domain, Private and Public Firewalls disabled. I then checked the persistent routes and the necessary routes are in in place, but they are not showing up under the active routes. Persistent Routes dynamically move to the active routes section if they are valid and reachable. Based off this information, it appears there is some application or tool in place at the OS level that is preventing the instance from reaching the 169.254.169.254 address. Is there any other type of firewall, proxy, or IPSec software installed on the instances? If so, can you please provide us with some information about the software/tool and how it is configured.

In order to further test this, can you please launch a vanilla instance from an AWS and see if you can reach the proxy address mentioned in the link below

The following link “http://169.254.169.254/latest/meta-data/” should be accessible in each EC2  instance and link below explains in better details and few other links you can test with

https://docs.aws.amazon.com/en_us/AWSEC2/latest/WindowsGuide/ec2-instance-metadata.html

If the link above does not work, this is most likely an application that may be causing it – in order to eliminate the cause to see if it is the AWS AMI, you can build a base windows server and see if you can access the link on the new server and if you can then  this most likely points to the something that is installed on the server or a bad AMI

The 169.254.169.254 is the link-local address where you can access metadata for your instance and should be reachable from the EC2 instance

 

Leave a Reply

Your email address will not be published. Required fields are marked *

*
*