ERROR : precheck.txt: Failed to copy: InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records. [BUG]

[ShakeelHussain]

Describe the bug
We are trying to use backup repo with aws s3

To Reproduce
Steps to reproduce the behavior:
run kbcli to create backup repo with aws access key and secret
kbcli backuprepo create my-repo
--provider s3
--region ap-southeast-1
--bucket mongodb-backup-bucket
--access-key-id
--secret-access-key <ACCESS_KEY>
--access-method Tool --default

[zjx20]

Hi @ShakeelHussain, this error message is returned by AWS, indicating that the AK/SK you provided is invalid. Please make sure you didn't make a typo while typing in the command line.

You can also try using the s3cmd tool to verify whether the AK/SK is valid, for example:

brew install s3cmd

s3cmd --access_key <ACCESS_KEY> \
      --secret_key <SECRET_KEY> \
      --region ap-southeast-1 \
      ls

[weicao]

Hi @ShakeelHussain, this error message is returned by AWS, indicating that the AK/SK you provided is invalid. Please make sure you didn't make a typo while typing in the command line.

You can also try using the s3cmd tool to verify whether the AK/SK is valid, for example:

brew install s3cmd

s3cmd --access_key <ACCESS_KEY> \
      --secret_key <SECRET_KEY> \
      --region ap-southeast-1 \
      ls

@ShakeelHussain does it solve your problem?

[shaarif-khan]

I am facing the same issue; I have been providing the sts token of the assume role which has s3AllAccess, but I guess I have to provide some other access_key and secret_key. could you please guide me which credentials to provide?

[zjx20]

I am facing the same issue; I have been providing the sts token of the assume role which has s3AllAccess, but I guess I have to provide some other access_key and secret_key. could you please guide me which credentials to provide?

@shaarif-khan
KubeBlocks currently doesn't support using the sts token, you will have to use the accessKey and secretKey mechanism.

Please follow this doc from AWS to obtain your credentials. And then try again with:

# Note: the keys in this command are from the AWS doc, and you should replace them with yours.
kbcli backuprepo create my-repo \
  --provider s3 \
  --region ap-southeast-1 \
  --bucket your-bucket \
  --access-key-id "AKIAIOSFODNN7EXAMPLE" \
  --secret-access-key "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY" \
  --access-method Tool --default

[shaarif-khan]

@zjx20 Thankyou that worked,
is there any future plan to have a feature to use assume role credentials with it?

[zjx20]

@zjx20 Thankyou that worked, is there any future plan to have a feature to use assume role credentials with it?

I'm afraid not, but could you tell us more about your use case and why you need to use AssumeRole?

[github-actions]

This issue has been marked as stale because it has been open for 30 days with no activity

[zjx20]

Close for now. Require more input from users.