You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The AWS option currently only supports cases wherein a permanent access/secret key is supplied as arguments, not for temporary keys (such as those retrieved via STS). This is a common use case, wherein a user can authenticate via something other than having their own IAM user, and can then be given credentialed access to various AWS endpoints (for instance, access to an API in the API Gateway).
Fixing this is extremely simple (though there's a limitation in the aws4 library in certain cases that requires knowledge of AWS, see mhart/aws4#30 for details), and I'll be submitting a PR for it.
The text was updated successfully, but these errors were encountered:
lostcolony
pushed a commit
to lostcolony/request
that referenced
this issue
Nov 17, 2016
The AWS option currently only supports cases wherein a permanent access/secret key is supplied as arguments, not for temporary keys (such as those retrieved via STS). This is a common use case, wherein a user can authenticate via something other than having their own IAM user, and can then be given credentialed access to various AWS endpoints (for instance, access to an API in the API Gateway).
Fixing this is extremely simple (though there's a limitation in the aws4 library in certain cases that requires knowledge of AWS, see mhart/aws4#30 for details), and I'll be submitting a PR for it.
The text was updated successfully, but these errors were encountered: