NS8 Backup to S3 Authentication Failure

bwdjames · June 15, 2024, 9:30pm

NethServer Version: NS8 (fully up-to-date)
Module: Backup.

I am attempting to configure the Backup to S3 and it appears to be fairly straight forward but I must be misconfigured one of the options as I receive the error message “Cannot authenticate”.

I know the AWS Access Key ID and Secret Access Key is correct as I have tested it on the command line successfully with the need for any other passwords.

I did have a look at the NS8 Backup Module Documentation and it is not giving very specific details for the different options, eg the format of the AWS S3 Bucket Name.

The only other item which I may be entering incorrectly is the AWS S3 Bucket Name.

What format should the AWS S3 Bucket Name take?

Also, what are the requirements for the Repository Name?

LayLow · June 15, 2024, 10:09pm

Just providing as a reference FYI

github.com/NethServer/dev

backup: cannot configure OVH S3 object storage as destination repo

opened 02:33PM - 31 May 24 UTC

nrauso

bug

NS8 does not allow to configure the OVH S3 object storage as backup repo. **S…teps to reproduce** - Create new bucket on OVH S3 object storage - Try to connect it to NS8 as new backup repo **Expected behavior** The new repo should be available and reachable **Actual behavior** The repo adding procedure generates an error: ``` ~]# redis-cli --raw get task/cluster/8c1370e2-ce2e-49f0-b796-ed356a318f5d/output [{"field": "parameters", "parameter": "parameters", "value": "2024/05/29 09:52:16 Failed to size: AuthorizationHeaderMalformed: The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'sbg'\n\tstatus code: 400, request id: tx787f64f6cea340d2826ed-006656fad0, host id: tx787f64f6cea340d2826ed-006656fad0\n", "error": "backup_repository_not_accessible"}] ``` The issue seems related to the [lack of mandatory additional attributes](https://help.ovhcloud.com/csm/it-public-cloud-storage-s3-rclone?id=kb_article_view&sysparm_article=KB0047466) needed by `rclone`. **Components** - Core 2.8.1

bwdjames · June 16, 2024, 2:30pm

Thanks for the reference @LayLow , that appears to be for the OVH S3 option and not the AWS (Amazon) S3 option so not quite sure if that bug will apply to both.