-
-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] netkan.exe no longer able to successfully use IAM #3112
Comments
Maybe they changed the EDIT: My testing script sets both vars, and it doesn't help. 👎 EDIT II: Hmm, even a pre-#3108 netkan.exe doesn't work with my test script anymore, so I may not be very much help in this... |
BTW WTH is IAM? |
Identity Access Management |
Also, this may have caused a bit of problem with mods that had updated during this outage. I know of two that are not correctly reporting in CKAN Last known good updates were to: |
Yeah, the bot's broken. Please bear with us. |
Is it proxy related? |
Background
Noted nothing had been checked in 15 hours when I was curious to see if the GitHub outage was impacting indexing.
Problem
I am trying to get some more info, this applies specifically to IAM via EC2, testing locally the latest image is able to use token auth just fine.
It does line up with a merge that update the AWSSDK. One thing that is making it awkward is we have to use 'Shell Form` for our entrypoint, making it quite difficult to pass in a debug flag via the task definition.
Debug output doesn't tell us a whole lot more
The text was updated successfully, but these errors were encountered: