S3Credentials issues

Created on 22 February 2023, over 1 year ago
Updated 15 March 2023, over 1 year ago

Problem

We are currently seeing an error on our site and have no clue as to what could have changed to effect this and curious if anyone else has been seeing this recently. I'm not an AWS or s3 expert by any means.

The error:
Aws\Exception\CredentialsException: Error retrieving credentials from the instance profile metadata service. (cURL error 28: Connection timed out after 1000 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)) in Aws\Credentials\InstanceProfileProvider->handleRetryableException() (line 264 of /code/vendor/aws/aws-sdk-php/src/Credentials/InstanceProfileProvider.php).

We are currently running on Drupal 9.5.0 and this module is 8.x-3.1. We are also using the S3 File System CORS Upload at 8.x-1.0-rc2.

Currently just having a hard time narrowing down the root issue and trying to get as much info as I can. Hopefully its just a small thing I'm overlooking. If there is any other info I can provide please let me know.

πŸ’¬ Support request
Status

Fixed

Version

3.1

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States pingevt

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • 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
  • πŸ‡ΊπŸ‡ΈUnited States pingevt

    Thank @cmlara, this give me a lot to run down!

  • Status changed to Fixed over 1 year ago
  • πŸ‡ΊπŸ‡Έ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.

Production build 0.69.0 2024