[🐛 BUG]: Region is missing from SQS endpoint URL when RR is running inside EC2 about roadrunner HOT 9 CLOSED

@rustatian thanks for a fast response :)

Regarding the global sqs key, I think that a better flow would be to always respect the explicitly provided configuration

So priority would be:

1. If there is sqs key and there are credentials/configs provided, use them
2. Use credentials from the EC2 instance (current flow)

Let me know if you need any additional info regarding the endpoint region issue.

from roadrunner.

Ok, since I can't control the changed behavior in the AWS SDK, the global configuration would be able to override the existing IAM values since the next bugfix version (2023.3.9)

from roadrunner.

Hey @matteokov 👋
Yeah, RR tries to perform a call to the well-known local URL to check if it is running inside AWS environment.
The global sqs key ignored in that case (which might be a wrong decision btw).
I'll double-check that behavior because configuration from inside AWS is managed by the AWS Golang package...

from roadrunner.

Yeah, I'm currently verifying your info, but anyway, in 2024.1 I'll update this behavior (since this is a BC).

from roadrunner.

@matteokov Could you please try to set AWS_REGION env variable and restart RR?

from roadrunner.

@rustatian This fixed an issue and RoadRunner started normally

from roadrunner.

It looks like a bug in the AWS GO SDK, I found an issue stating about the same problem.

from roadrunner.

But, I found a way how to support both, the global sqs config with the data provided by the IAM.

from roadrunner.

The fix will be released next Thursday.

from roadrunner.