The new S3 storage - confusing fields?

[fribse]

I was very excited to see the new S3 storage option, but the configuration seems overly complicated

From the PBS


Why do I have to create a pattern in the 'Endpoint' field?
I mean I have several backup systems going to the s3 storage, I've never seent that before?
It is quite confusing.
The rest is logical I guess.
But what of the local cache I have to set up, how big is that supposed to be?

 

[TrustyHippo]

I use BackBlaze S3, and it's very straight forward.

• Endpoint is the FQDN of my Backblaze bucket
• Access/Secret key are directly from BackBlaze
• I had to check "Path Style" for it to work

 

[Chris]

I use BackBlaze S3, and it's very straight forward.

• Endpoint is the FQDN of my Backblaze bucket
• Access/Secret key are directly from BackBlaze
• I had to check "Path Style" for it to work

View attachment 89521

For backblaze I would recommend the config as mentioned here https://forum.proxmox.com/threads/b...s-on-s3-endpoint-pbs4-0-14.169733/post-792874

 

[Chris]

I was very excited to see the new S3 storage option, but the configuration seems overly complicated

From the PBS
View attachment 89512

Why do I have to create a pattern in the 'Endpoint' field?
I mean I have several backup systems going to the s3 storage, I've never seent that before?
It is quite confusing.
The rest is logical I guess.
But what of the local cache I have to set up, how big is that supposed to be?

The reason to use the patterns in the endpoint is so the same endpoint configurations can be reused for multiple buckets/datastores. Since the bucket is part of a datastore configuration, it is recommended to use the {{bucket}} pattern as placeholder (if you use vhost style bucket addressing that is).

The region is also part of the AWS request signature scheme, used to athenticate requests to the api. Therefore it is required to set it in it's dedicated field, the {{region}} pattern currently only being for convenience. You can set it manually as well, but it's recommended to use the pattern.

 

[TrustyHippo]

For backblaze I would recommend the config as mentioned here https://forum.proxmox.com/threads/b...s-on-s3-endpoint-pbs4-0-14.169733/post-792874

Ok I modified my configuration to use the more complicated method. Previously all was working fine, but on OCCASION a chunk would fail to verify. 99% of the time verification worked. So I'm not convinced a one off error that I can't reproduce on demand is caused by the endpoint config. But I made the change anyway.