This is for information should it help anyone.
I have multiple sites on different servers that back up to separate buckets on an S3 object storage server run by IONOS. They have been working fine for months with Signature Method set to v2 legacy mode and Bucket Access to path access (legacy). These are the recommended settings, however all post-processing stages across multiple sites started to fail after 15 October 2023 with the following message:
Akeeba\S3\Connector::startMultipart(): [500] SignatureDoesNotMatch:The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. For more information, see REST Authentication and SOAP Authentication for details. Debug info: SimpleXMLElement Object ( [Code] => SignatureDoesNotMatch [Message] => The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. For more information, see REST Authentication and SOAP Authentication for details. [RequestId] => … [HostId] => … )
It just so happens that I updated Akeeba Solo to v8.1.1 on 15 October 2023 but that may be coincidence.
After some experimentation, the solution I've found is to change:
- Signature Method : v4 (preferred for Amazon S3)
- Amazon S3 Region: Europe, Central (Frankfurt) [-> chosen to match the same location as the IONOS server ]
Bucket access and IONOS' S3 custom endpoint can remain as they were. The post-processing stage and manual transfer to server now work again on all sites.
Whether this is due to a change at IONOS (I have had no notification to this effect) or a change in Akeeba Solo since version 8.1.1 I can't say.
