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
Currently the AWS SDKs do not allow for creds to be specified at the request level, only at the client level.
Use Case
There are many valid use-cases where a web service might want to make requests with different creds. A good example is a web service interacting with customer resources. Amazon recommends a pattern where the web service can use creds to isolate permissions to resources owned by the customer making the call (talk, iam feature helping with federated creds).
The SDK clients handle tcp connection pooling which provides better performance and fewer higher-percentile spikes than you get if you create a new client and new TCP connections on every call.
Proposed Solution
It would be a benefit to SDK customers to support this use-case in the SDK by providing a mechanism to override the creds provider on a per-request basis so that customers using a federated connection model aren't hurt by needing to create a new sdk each time they want to change creds.
Other Information
I'm asking this question in the aws-sdk-rust repo because the SDK I want this for is Rust, but this applies to the AWS SDKs more generally. As far as I know no sdk in any language supports a documented interface for this, but it can be achieved in some languages with looser controls like javascript.
Acknowledgements
I may be able to implement this feature request
This feature might incur a breaking change
A note for the community
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue, please leave a comment
The text was updated successfully, but these errors were encountered:
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the feature
Currently the AWS SDKs do not allow for creds to be specified at the request level, only at the client level.
Use Case
There are many valid use-cases where a web service might want to make requests with different creds. A good example is a web service interacting with customer resources. Amazon recommends a pattern where the web service can use creds to isolate permissions to resources owned by the customer making the call (talk, iam feature helping with federated creds).
The SDK clients handle tcp connection pooling which provides better performance and fewer higher-percentile spikes than you get if you create a new client and new TCP connections on every call.
Proposed Solution
It would be a benefit to SDK customers to support this use-case in the SDK by providing a mechanism to override the creds provider on a per-request basis so that customers using a federated connection model aren't hurt by needing to create a new sdk each time they want to change creds.
Other Information
I'm asking this question in the aws-sdk-rust repo because the SDK I want this for is Rust, but this applies to the AWS SDKs more generally. As far as I know no sdk in any language supports a documented interface for this, but it can be achieved in some languages with looser controls like javascript.
Acknowledgements
A note for the community
Community Note
The text was updated successfully, but these errors were encountered: