You can put Bunny in front of images.prismic.io to cache images and reduce origin hits, but it’s not our default recommendation. Prismic already uses imgix’s CDN with dynamic optimization (WebP/AVIF, quality, sizing). Adding another CDN can break format negotiation or sizing, and we can only provide limited support outside of our recommended setup. Also note we can’t whitelist Bunny IPs on the Prismic side; those IP lists are for your own firewall rules and they change regularly.
I agree, it’s not the best set up. Said that, we have around 12 to 1 image to content api requests and i cannot really optimise the image api requests. Seems like each image view counts as one api request. At least that’s what i can figure out from the dashboard.
When it comes to whitelisting ips from bunny. That’s ok, but can you at least tell me if that’s not gonna trigger your own firewall rules? It might be seen as a DDOS otherwise and my site might stop working correctly.
We don’t think it should be an issue, so you could give it a go, but take that with a grain of salt as some of it might depend on Imgix’s configurations as well. On our end it’ll be fine, and if anything happens, you can always link this forum thread in any ticket you raise and we’ll know exactly what to look into