How rclone can read the realtime ak/sk/securytoken
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 59.8k
- Forks
- 5.4k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 48
Description
In practical scenarios, we are often limited to using temporary access keys, secret keys, and security tokens to access S3, which typically expire after a few hours.
When utilizing rclone mount, we don't seem to have a way to directly perceive or address the expiration of these authentication credentials.
My question is, is there a method to dynamically update and maintain these credentials while they're in use, ensuring the mounted S3 directory remains accessible without any interruptions caused by their expiration?
Your insights are eagerly awaited, and I sincerely hope to hear back from you soon.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or an entry point. First clarify whether rclone mount should refresh temporary S3 credentials automatically, then identify the relevant mount and S3 credential-handling areas; done would mean a mounted S3 directory remains accessible as credentials expire and renew.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100