temporalio / temporalio/temporal
AWS STS for connecting S3 for archival
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Hi Team,
Problem Statement
We are using a self-hosted Temporal service and attempting to enable the archival feature. However, we are unable to access AWS S3 from the Temporal service because it does not support AWS STS. The Temporal server requires actual access_key and secret, but due to infrastructure restrictions, we cannot use actual AWS credentials. Our infrastructure supports STS, but the Temporal server does not. Is there an alternative solution that can work in this scenario?
Expected Behavior
temporal server should be able to connect with S3 bucker and archive.
Actual Behavior
getting 403
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 Temporal archival configuration for S3 credentials and the AWS authentication path; the issue provides no file or test entry point. Reproduce the reported 403 with the described infrastructure, then define done as connecting to the S3 bucket through STS and successfully archiving data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100