Create backup storage fails - invalid request invalid bucketName

[Michael_Shield]

Hi,

I’ve been using Everest to create test DB’s for both MongoDB and Postgresql on a Hetzner Kubernetes cluster. Came back to create backup storage for Postgres in S3, which failed due to the bucket name format containing full stops.

So a new bucket was created with a more standard name, and access tested using the s3cmd utility.

root@vr22 ~ # s3cmd -c /root/.ms-s3cfg put haproxy.cfg s3://outdoor-active-everest-test/
upload: ‘haproxy.cfg’ → ‘s3://outdoor-active-everest-test/haproxy.cfg’ [1 of 1]
7330 of 7330 100% in 0s 21.34 KB/s done
upload: ‘haproxy.cfg’ → ‘s3://outdoor-active-everest-test/haproxy.cfg’ [1 of 1]
7330 of 7330 100% in 0s 57.89 KB/s done
root@vr22 ~ # s3cmd -c /root/.ms-s3cfg info s3://outdoor-active-everest-test/
s3://outdoor-active-everest-test/ (bucket):
Location: eu-west-2
Payer: BucketOwner
Expiration Rule: none
Policy: none
CORS: none
ACL: 50459b1a7c8542464d1c71746fe30d82ce4aa05da24e3039e4bcc3e523004e79: FULL_CONTROL

But following the online instructions and matching the required params, we get the following failure

invalid request invalid bucketName

Two screen shots included to show the settings used, and the buckets as seen in AWS.

Any suggestions as to what might be going wrong.

Thanks,

Mike

[Michael_Shield]

Hi, all sorted.

There is still an issue in that you are allowed to create backup storage with a dotted notation in the bucket name, but are not allowed to use it. Also, the create backup storage web page auto fills the endpoint url and the first part of the AWS access key with the Admin user and it’s credentials, but that’s a minor point.

In the end, just down to having to tight an access level on the new bucket, once corrected an unscheduled backup completed in about 2 mins, so testing moves on to other apps. Cheers, Mike