If you need S3-compatible access, create a fresh zone with S3 Compatibility enabled from the start, do not try to retrofit it. Wire clients with zone name as the access key, zone password as the secret, and the region-specific endpoint. Use path-style addressing (endpoint/bucket/key), virtual-hosted style does not work.

Context: Official docs (bunny.net, S3 compatibility): S3 access is a choice you make when you create the storage zone, by enabling the S3 Compatibility option on the creation form. It cannot be switched on for an existing zone afterward. The S3 credentials also surprise people: the Access Key ID is the storage zone name itself and the Secret Access Key is the zone password, with a per-region endpoint like https://YOUR-region-s3.storage.bunnycdn.com and path-style URLs only.