# Rancher backup helm chart

**URL:** <https://forums.suse.com/t/rancher-backup-helm-chart/20655>\
**Category:** SUSE Rancher Prime\
**Created:** [July 6, 2021, 7:38am UTC](https://forums.suse.com/t/rancher-backup-helm-chart/20655 "2021-07-06T07:38:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Harri](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/harri/32/6207_2.png) [@Harri](https://forums.suse.com/u/Harri)\
**Post date:** [July 6, 2021, 7:38am UTC](https://forums.suse.com/t/rancher-backup-helm-chart/20655/1 "2021-07-06T07:38:14Z")

</div>

I have a question about the rancher backup helm chart, provided on Apps & Marketplace: Is it reasonable to install the chart using “No default storage location”?

---

<div class="post-metadata">

**Author:** ![superseb](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/superseb/32/2424_2.png) [@superseb](https://forums.suse.com/u/superseb)\
**Post date:** [July 6, 2021, 6:50pm UTC](https://forums.suse.com/t/rancher-backup-helm-chart/20655/2 "2021-07-06T18:50:48Z")

</div>

Depends on what you are looking for/what you are trying to do. The documentation on this is here: [Rancher Docs: Backup Storage Location Configuration](https://rancher.com/docs/rancher/v2.5/en/backups/configuration/storage-config/#no-default-storage-location)

---

<div class="post-metadata">

**Author:** ![ealasgarov](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/ealasgarov/32/8064_2.png) [@ealasgarov](https://forums.suse.com/u/ealasgarov)\
**Post date:** [October 5, 2021, 2:09pm UTC](https://forums.suse.com/t/rancher-backup-helm-chart/20655/3 "2021-10-05T14:09:14Z")

</div>

Hi Seb, you seem to be active on the topic, do you have any idea what could it be that the backup operator spits below error when I initiate backup (aws s3 storage set as a default location)?  
Credentials are stored as a secret in cattle-resources-system ns. I did everything according to instructions on the link you’ve quoted.  
Thanks in advance!

`failed to check s3 bucket:rancher-backup-mybucketname, err:Head https://rancher-backup-mybucketname.s3.dualstack.eu-west-1.amazonaws.com/: net/http: invalid header field value "AWS4-HMAC-SHA256 Credential=\x00\xa2\x00H\xa3\x83H\xf8AU0\xb7\xe0\x93\xd2/20211006/eu-west-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=937ba5ac52dc2bfe979ba16da25dbd02c8ea6be772d00da12a76f7764cf5dba0" for key Authorization`

---

<div class="post-metadata">

**Author:** ![dstuart](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/dstuart/32/5598_2.png) [@dstuart](https://forums.suse.com/u/dstuart)\
**Post date:** [February 23, 2022, 12:19pm UTC](https://forums.suse.com/t/rancher-backup-helm-chart/20655/4 "2022-02-23T12:19:29Z")

</div>

Hi, did you find a solution to this. I am getting this error in v2.5.2.

Update. The fix I found for this is in how you create the sec creds.  
I initially created the base64 by echo accesskey or secret | base64  
It needed to be echo -n “” | base64 and echo -n “” | base64

---

<div class="post-metadata">

**Author:** ![GoranTornqvist-Conoa](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/gorantornqvist-conoa/32/9737_2.png) [@GoranTornqvist-Conoa](https://forums.suse.com/u/GoranTornqvist-Conoa)\
**Post date:** [January 4, 2023, 7:36am UTC](https://forums.suse.com/t/rancher-backup-helm-chart/20655/5 "2023-01-04T07:36:28Z")

</div>

Nice, echo -n \*\*\* | base64 worked for me as well! Thanks …