diff --git a/content/rancher/v2.x/en/backups/v2.5/configuration/backup-config/_index.md b/content/rancher/v2.x/en/backups/v2.5/configuration/backup-config/_index.md index d86ea7fcb64..930d5339946 100644 --- a/content/rancher/v2.x/en/backups/v2.5/configuration/backup-config/_index.md +++ b/content/rancher/v2.x/en/backups/v2.5/configuration/backup-config/_index.md @@ -139,6 +139,12 @@ data: secretKey: ``` +Make sure to encode the keys to base64 in YAML file. +Run the following command to encode the keys. +``` +echo -n "your_key" |base64 +``` + ### IAM Permissions for EC2 Nodes to Access S3 There are two ways to set up the `rancher-backup` operator to use S3 as the backup storage location. @@ -182,4 +188,4 @@ After the role is created, and you have attached the corresponding instance prof # Examples -For example Backup custom resources, refer to [this page.](../../examples/#backup) \ No newline at end of file +For example Backup custom resources, refer to [this page.](../../examples/#backup)