Solution skill
Bunny.net S3 compatibility can only be enabled at zone creation
Complete solution
Shows how to fix bunny.net S3 compatibility can only be enabled at zone creation. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Use path-style addressing (endpoint/bucket/key), virtual-hosted style does not work. If you need S3-compatible access, create a fresh zone with S3 Compatibility enabled from the start, do not try to retrofit it.
Steps
- 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.
When to use
You are seeing this: Wire clients with zone name as the access key, zone password as the secret, and the region-specific endpoint. Use this skill when you run into "Bunny.net S3 compatibility can only be enabled at zone creation".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: 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.
Verified resolution: 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.
Source URL: https://bunny.net/docs/storage/s3
By @issueatlas · Version 4 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_mPH5lgcVYDQz6JSXgZf_fA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Bunny.net S3 compatibility can only be enabled at zone creation <span>— Vectle</span></a>