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
One user ( #122 ) was trying to authenticate with a Session or a Federation token, i.e. with the data returned in a STS Credentials response.
If some organizations are using things like STS to give limited-duration leased credentials to their users, then it is probably a good idea for awslimitchecker to support these, so people can evaluate it without needing administrative approval.
The text was updated successfully, but these errors were encountered:
Using 0.7.0, STS credentials work fine with awslimitchecker if I export the AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_SESSION_TOKEN environment variables.
One user ( #122 ) was trying to authenticate with a Session or a Federation token, i.e. with the data returned in a STS Credentials response.
If some organizations are using things like STS to give limited-duration leased credentials to their users, then it is probably a good idea for
awslimitchecker
to support these, so people can evaluate it without needing administrative approval.The text was updated successfully, but these errors were encountered: