- Issue created by @pingevt
- 🇺🇸United States cmlara
The error message indicates the following:
- No specific credentials have been configured (or are empty) and we are 'falling back' to attempting to obtain authentication using instance credentials
- That the instance credential service did not respond
Possible causes that I can think of for not receiving a response are:
- The Drupal host is not an AWS instance, see readme to configure credentials for non metadata based login
- The instance metadata service has been blocked, refer to AWS configuration regarding unblocking the metadata endpoint
- Possibly rate limits, however I believe rate limits should return a 4xx or 5xx series error code and not a timeout, the readme documents how to cache credentials to avoid metadata server lookups
- Other internal AWS issues, though unlikely are always a possibility, this would likely require working with AWS support
- Status changed to Fixed
almost 2 years ago 5:23am 15 March 2023 - 🇺🇸United States cmlara
Since this issue has had over 2 weeks without additional posts I'm going to assume that the previous information provided was able to lead to a solution and mark the issue fixed.
If this is not the case you can re-open the issue and provide additional details.
- 🇺🇸United States pingevt
Yes thank you @cmlara! Ultimately ended up being a credentials issue but your feedback helped me track it all down.
Automatically closed - issue fixed for 2 weeks with no activity.