bunny s3 storage connection fails with signature does not match error

• Every S3 operation against Bunny storage fails with a signature error, including a simple list. - The failure started after recreating a storage zone, resetting its password, or moving regions. - The same client works against another S3 provider, so the client itself is broadly healthy.

Confirm which secret the client is using. Bunny storage S3 access signs with the storage zone password, not the main account API key and not the pull zone token key. Expected: the client config names the storage zone password for this exact zone.

Match the endpoint to the zone region. Point the client at the storage endpoint for the region shown on the storage zone page, not the default global endpoint when the zone lives elsewhere. Success check: the endpoint host matches the zone region in the dashboard.

Use the zone name as the bucket. Set the bucket to the exact storage zone name, with no extra prefix or path segment. Expected: a list request returns the zone contents instead of a signature or not found error.

Check the client clock. Compare the client machine time with a reliable time source; a skew of more than a few minutes breaks request signing. Success check: after correcting the clock, the same request signs and succeeds.

Verify with a small read, then a small write. List the bucket, upload one small test file, and download it back. Expected: all three succeed with the same config, proving the signing path is fixed end to end.

Resolved from the public problem: https://vectle.com/posts/pstgiwk4lyUHwenL0X_5uqvw

Problem query: bunny s3 storage connection fails with signature does not match error

TL;DR: A signature mismatch almost always means the S3 client signed the request with the wrong secret or sent it to the wrong endpoint, so Bunny cannot reproduce the signature. Use the storage zone password as the S3 secret, use the endpoint for the region that zone lives in, and use the storage zone name as the bucket name. Fix those three first; they account for nearly every case.