Anyone got OVH Cloud S3 Compatible storage to work?

[sunbeam60]

I’ve created an S3 container on OVH Cloud (RBX region):

The user has full rights on the container:

The Duplicati configuration is set up with this user and access key:

… yet I continue to get: “Failed to connect: The AWS Access Key Id you provided does not exist in our records.”

I have triple checked and copy pasted the information a million times. The user and the access key is copied straight from OVH Cloud’s user panel.

I’m sure I’m doing something obvious, but I really cannot, for the life of me, figure out what it is.

Is there anyone who has a working S3 Compatible Object Storage location from OVH Cloud set up as a backup destination?

[ts678]

Welcome to the forum @sunbeam60

Object Storage - Identity and access management (OVH)

shows a picture with “S3 username”, “S3 access key”, and “S3 secret key”.

Manage access keys for IAM users (AWS)

has “access key id” and “secret access key”.

So both have a secret part, which is probably what you typed where the asterisks are.
For “AWS Access ID”, it looks like you typed user, which may be an unknown S3 idea.

@sunbeam60

The user and the access key is copied straight from OVH Cloud’s user panel.

Have you tried copying the panel “S3 access key” instead of its “S3 username”?

If so, I’m not sure what’s up, and you might need to wait for an actual OVH user.

Here’s a bit of an OVH image that might explain the S3 credentials in its last line:

Variations in terminology have thrown people off, but usually there’s a secret part.
There’s also a one-to-one less secret part. User does not sound like a one-to-one.

[sunbeam60]

Really appreciate the answer. There is a secret, which I had ignored since the “user” and “access key” had a perfect name mapping to Duplicati. I’ve not tried using “access key” from OVH as the username in duplicati and “secret” from OVH as “access key” in duplicati so will give that a go.

In the mean time would still love to hear from anyone successfully using OVH S3 compatible object storage as a Duplicati destination.

[ts678]

@sunbeam60

There is a secret, which I had ignored since the “user” and “access key” had a perfect name mapping to Duplicati.

“S3 access key” to “AWS Access Key” is close. “S3 Username” to “AWS Access ID” isn’t.
Regardless, most authentication schemes are based on secrets, and a secret is required.

I don’t like the tags that Duplicati puts in the GUI, so I checked, and new UI has improved:

which matches AWS terminology. The manual isn’t really updated for latest Beta yet, but

S3-compatible Destination (which covers URL syntax) has terminology and hints like this:

s3://<bucket name>/<prefix> ?aws-access-key-id=<account id or username> &aws-secret-access-key=<account key or password> &s3-servername=<server ip or hostname> &use-ssl=true

There are certainly similarities to username/password, but OVH adds non-S3 username.

The old UI in latest Beta still has the terminology I don’t like that deviates from S3 terms:

so is possibly an area for improvement – except I’m not sure if the old UI is a dev priority.

@sunbeam60

I’ve not tried using “access key” from OVH as the username in duplicati and “secret” from OVH as “access key” in duplicati so will give that a go.

I’m pretty certain that’s the right mapping, but that doesn’t mean all will work. Hoping…

[sunbeam60]

So, yeah, you were right.

What Duplicati calls “AWS Access ID”, OVH Cloud calls “Access Key” …
and what Duplicati calls “AWS Access Key”, OVH Cloud calls “Secret Key”.

So, in other words, in the Duplicati backup job:

• Set “AWS Access ID” to OVH’s “Access Key”
• Set “AWS Access Key” to OVH’s “Secret Key”

Thanks for the help - I’m not sure I would have thought to try this combination.

[ts678]

I’m glad it worked. In new UI now in Beta which uses AWS terminology, it’s probably:

• Set “AWS Access Key ID” to OVH’s “Access Key”
• Set “AWS Secret Access Key” to OVH’s “Secret Key”

I hope that makes a bit more sense. I like these terms better, but mainly they’re AWS.