Issues with backups on couchbase version 7.6.2

[sruthimaddileti]

Hello,

I’ve installed couchbase 7.6.2 and tried running a config command with S3 as staging path. Below is the command :

“/opt/couchbase/bin/cbbackupmgr” config --archive “s3://yb-apsouth1/couchbase/Backup_250/beer-sample” --repo “cv_beer-sample” --include-buckets “beer-sample” --obj-staging-dir “/opt/cv” --obj-access-key-id <accesskey_id> --obj-secret-access-key <secret_access_key> --obj-region ap-south-1 --obj-endpoint s3.amazonaws.com

below is the error :

Warning: --include-buckets is deprecated, use -/–include-data
Backup repository creation failed: failed to lock remote archive: failed to create lockfile object with key ‘couchbase/Backup_250/beer-sample/lock-6db8abaf-a00b-4d9c-a556-9b1370e0828e.lk’: operation error S3: PutObject, resolve auth scheme: resolve endpoint: endpoint rule error, Custom endpoint s3.amazonaws.com was not a valid URI

The same command worked fine with version 7.6.1 and 7.6.0.

I tried passing the endpoint as ‘https://s3.amazonaws.com’ and the command worked fine in 7.6.2.

Can someone please let me know if there are any changes in 7.6.2 around this?

Thanks and regards,
Sruthi Maddileti.

[saf]

Hi @sruthimaddileti. I was able to reproduce the behaviour you mention here. While there was no direct changes with how cbbackupmgr handles custom endpoints in 7.6.2, the AWS SDK used by cbbackupmgr was upgraded in 7.6.2. It seems that the old AWS SDK silently prepended “https://” to endpoints without a scheme, whereas the new SDK returns an error instead.

Thanks for raising this, I created Loading... to track this issue. In the meantime, I recommend always making sure any endpoints you pass to cbbackupmgr are valid URIs to avoid errors.

Thanks,

Safian Ali