Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add AWS Session Token support #1039

Closed
jhsmith opened this issue Oct 11, 2018 · 2 comments
Closed

Add AWS Session Token support #1039

jhsmith opened this issue Oct 11, 2018 · 2 comments
Labels
area/artifacts S3/GCP/OSS/Git/HDFS etc solution/superseded This PR or issue has been superseded by another one (slightly different from a duplicate) type/feature Feature request

Comments

@jhsmith
Copy link

jhsmith commented Oct 11, 2018

This is a feature request.

Please add support for AWS session tokens as an optional credential for S3 access. In our corporate account we have to use session tokens in addition to the access key and secret key when doing local development.

I see that you create a minio client with NewWithRegion. It looks like you could pass in a Session Token you instead use NewWithCredentials instead.
@jessesuen jessesuen added the type/feature Feature request label Apr 20, 2019
@alexec alexec added the area/artifacts S3/GCP/OSS/Git/HDFS etc label Feb 7, 2022
@mocsharp
Copy link

mocsharp commented May 2, 2022

Any workaround for using temporary credentials and a session token to access MinIO artifact store?

@mocsharp mocsharp mentioned this issue May 3, 2022
Closed
@JacobHenner JacobHenner mentioned this issue Feb 6, 2023
Closed
@agilgur5
Copy link
Contributor

agilgur5 commented Sep 6, 2024

This was superseded by #5446 which has more upvotes and PRs out to be merged soon.

@agilgur5 agilgur5 closed this as completed Sep 6, 2024
@agilgur5 agilgur5 added the solution/superseded This PR or issue has been superseded by another one (slightly different from a duplicate) label Sep 6, 2024
@argoproj argoproj locked as resolved and limited conversation to collaborators Sep 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area/artifacts S3/GCP/OSS/Git/HDFS etc solution/superseded This PR or issue has been superseded by another one (slightly different from a duplicate) type/feature Feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@jhsmith @alexec @mocsharp @agilgur5 @jessesuen