AWS_ACCESS_KEY_ID
and AWS_SECRET_ACCESS_KEY
env not work for aliyun provider
#53463
Labels
affects-6.1
affects-6.5
affects-7.1
affects-7.5
affects-8.1
component/br
This issue is related to BR of TiDB.
may-affects-5.4
This bug maybe affects 5.4.x versions.
report/community
The community has encountered this bug.
severity/major
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
AWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
enviroment variablesfrom asktug: https://asktug.com/t/topic/1026409
after #34309, for Aliyun's provider will ignore the ak/sk in the environment variables
AWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
.2. What did you expect to see? (Required)
dumpling/br success with the env
AWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
ak/sk3. What did you see instead (Required)
dumpling/br failed
4. What is your TiDB version? (Required)
affect release-6.1, 6.5, 7.1, 7.5, 8.1
The text was updated successfully, but these errors were encountered: