Skip to content
This repository has been archived by the owner on Aug 16, 2022. It is now read-only.

Error assuming role #39

Closed
xino12 opened this issue Apr 22, 2021 · 4 comments
Closed

Error assuming role #39

xino12 opened this issue Apr 22, 2021 · 4 comments
Assignees

Comments

@xino12
Copy link

xino12 commented Apr 22, 2021

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:

Error: rpc error: code = Unknown desc = operation error EC2: DescribeRegions, exceeded maximum number of attempts, 10, https response error StatusCode: 0, RequestID: , request send failed, Post "https://ec2.aws-global.amazonaws.com/": dial tcp: lookup ec2.aws-global.amazonaws.com on 10.131.230.10:53: no such host

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.

@xino12
Copy link
Author

xino12 commented Apr 22, 2021

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 ?

@xino12
Copy link
Author

xino12 commented Apr 23, 2021

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
Copy link
Member

@xino12
Copy link
Author

xino12 commented Apr 26, 2021

🏆 thanks 🙇🏼

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants