updating to v5.12.0 results in a timeout error

• Expected behaviour: v5.12.0 should work like v5.11.0

• What actually happens:

...
loading Lambda config	sts.optInRegionalEndpoint
Error: connect ETIMEDOUT 169.254.169.254:80
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1129:14) {
  message: 'Missing credentials in config',
  errno: 'ETIMEDOUT',
  code: 'CredentialsError',
  syscall: 'connect',
  address: '169.254.169.254',
  port: 80,
  time: 2020-01-20T07:45:09.471Z,
  originalError: {
    message: 'Could not load credentials from any providers',
    errno: 'ETIMEDOUT',
    code: 'CredentialsError',
    syscall: 'connect',
    address: '169.254.169.254',
    port: 80,
    time: 2020-01-20T07:45:09.471Z,
    originalError: {
      message: 'EC2 Metadata roleName request returned error',
      errno: 'ETIMEDOUT',
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '169.254.169.254',
      port: 80,
      time: 2020-01-20T07:45:09.470Z,
      originalError: [Object]
    }
  }
}

• Steps to reproduce the problem: updated from v5.11.0 to v5.12.0, a downgrade fixes the problem

[adrai]

at least we learned something 😉

[adrai]

for me, yes… will use: AWS_ROLE_ARN