Support AWS STS (AWS_SESSION_TOKEN) for S3 Object Storage
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
Description of the change
Add sessionTokenKey to nextcloud.objectStore.s3.secretKeys once this https://github.com/nextcloud/server/issues/50579 is implemented.
Benefits
Support AWS STS for temporary credentials to access s3 object storage.
Possible drawbacks
-/-
Additional information
Currently, it is not possible to use dynamic, short-lived credentials with nextcloud to access s3...
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
Start by reviewing the Helm chart configuration for nextcloud.objectStore.s3.secretKeys and the upstream Nextcloud issue 50579. Add sessionTokenKey once upstream AWS STS support is implemented, then verify that the chart exposes the temporary credential setting for S3 object storage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100