Context
Per #4653 (comment), the historyserver S3 implementation uses non-standard environment variables for credentials:
AWS_S3ID instead of AWS_ACCESS_KEY_ID
AWS_S3Secret instead of AWS_SECRET_ACCESS_KEY
AWS_S3Token instead of AWS_SESSION_TOKEN
These should be migrated to the standard AWS environment variables so the historyserver follows AWS SDK conventions and works seamlessly with existing credential setups.
Scope
- Update
historyserver/pkg/storage/s3/s3.go to read from standard AWS env vars
- Update any related documentation and Helm chart values
Ref: #4652, #4653
Context
Per #4653 (comment), the historyserver S3 implementation uses non-standard environment variables for credentials:
AWS_S3IDinstead ofAWS_ACCESS_KEY_IDAWS_S3Secretinstead ofAWS_SECRET_ACCESS_KEYAWS_S3Tokeninstead ofAWS_SESSION_TOKENThese should be migrated to the standard AWS environment variables so the historyserver follows AWS SDK conventions and works seamlessly with existing credential setups.
Scope
historyserver/pkg/storage/s3/s3.goto read from standard AWS env varsRef: #4652, #4653