S3 Compatible - "Error: The key 'XXXX' is not valid (InvalidAccessKeyId)"

Here are some helpful tips to troubleshoot the error "Error: The key 'XXXX' is not valid (InvalidAccessKeyId)" when adding a S3 Compatible Destination on JetBackup 5.

  1. Ensure that the correct vendor is selected for the destination you will like to configure. Having the wrong vendor selected will use the wrong endpoints when authenticating the connection. If your vendor is not in the showcase, please refer to our docs on how to set a Custom Vendor.
  2. Be sure the access key, secret key, and bucket all match the configuration you have set in your S3 Compatible Vendor.

  3. Regions for each vendor can be selected by the dropdown. If the region you have configured is not within the list, please input the region manually by using "Custom Region". You can look up your region by logging into your vendor console and selecting your bucket.

 

If you find you are still having trouble adding your destination, please open a support ticket. 

  • 3 Users Found This Useful
Was this answer helpful?

Related Articles

Backblaze/S3 - Excessive Storage Use by JB5

We have received some reports of excessive Storage use by JetBackup 5 in the S3 Bucket. For...

My S3 Vendor is not included in the supported list on JetBackup 5?

You can find a small list of S3 Vendors that are supported with the new S3 Compatible plugin at...

S3 Common Issues / Failed to upload file

S3 destinations can often hit request limits when destinations are configured with high...

Unable to Validate Destination - SSH

JetBackup uses public-key authentication to connect to and validate your SSH Destination. This...

SSH Destination hitting "SSH Multiplexing Limit"

When receiving an error like the following: [ERROR] Failed transferring account "accountName"...