This repository has been archived by the owner on Aug 16, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 40
Error assuming role #39
Comments
I thought it might be related to #12 but when that happened I was able to fix it by setting that env var, now the problem seems like something else, probably something changed in the AWS sdk ? |
It seems that we're forced to use the same endpoint for STS and EC2, in our case we would like to be able to use the regional endpoint for EC2(as it seems that the global endpoint is not available) and use the global endpoint for STS service. Could we add a configuration parameter maybe? |
yevgenypats
added a commit
that referenced
this issue
Apr 25, 2021
yevgenypats
added a commit
that referenced
this issue
Apr 25, 2021
roneli
pushed a commit
that referenced
this issue
Apr 25, 2021
🏆 thanks 🙇🏼 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have setup the AWS_DEFAULT_REGION to aws-global in my ingestion jobs and it was working properly but now I see this error in the logs:
Are you aware whether something in AWS side has changed? I've looked for documentation and I can't see anything and AFAIK we're still assuming roles as we did in the past for other tools we use.
The text was updated successfully, but these errors were encountered: