We have been using DigitalOcean Spaces (S3) as a remote location for server backups with Amazon S3 Backup extension for a few years. There was no problem setting it up or using it.
Now, we have also started using Scaleway Object Storage (also S3 compatible) for backups storage and static files offloading, and it proved to be just a bit better (faster) than DO Spaces.
I thought it would be simple to use it also as Remote Storage for Plesk backups, again with Amazon S3 Backup extensions, but I failed to configure it.
I've tried different combinations of values but nothing worked.
Was someone successful setting up this combination of services (Scaleway Object Storage + Plesk Amazon S3 Backup extension)? Ideas?
Service provider: Custom
API Endpoint URL: https://s3.fr-par.scw.cloud
Login (Key): SC...
Password (Secret): sdfsaf-
Bucket: bigbox (tried: bigbox.s3.fr-par.scw.cloud, s3.fr-par.scw.cloud...)
Path: PSKbackup/ (tried: bigbox/PSKbackup/, /, /bigbox/...)
What I get is (bellow Bucket field): "Unable to check bucket and directory existence. Make sure you are using correct IAM policy (400 Bad Request (Request-ID: tx644298382a7242dcae00a-XXXef12bea))."
Now, we have also started using Scaleway Object Storage (also S3 compatible) for backups storage and static files offloading, and it proved to be just a bit better (faster) than DO Spaces.
I thought it would be simple to use it also as Remote Storage for Plesk backups, again with Amazon S3 Backup extensions, but I failed to configure it.
I've tried different combinations of values but nothing worked.
Was someone successful setting up this combination of services (Scaleway Object Storage + Plesk Amazon S3 Backup extension)? Ideas?
Service provider: Custom
API Endpoint URL: https://s3.fr-par.scw.cloud
Login (Key): SC...
Password (Secret): sdfsaf-
Bucket: bigbox (tried: bigbox.s3.fr-par.scw.cloud, s3.fr-par.scw.cloud...)
Path: PSKbackup/ (tried: bigbox/PSKbackup/, /, /bigbox/...)
What I get is (bellow Bucket field): "Unable to check bucket and directory existence. Make sure you are using correct IAM policy (400 Bad Request (Request-ID: tx644298382a7242dcae00a-XXXef12bea))."