Using ImageEngine with a 3rd party CDN

Now you can use a 3rd party CDN in front of ImageEngine if you wish. Even if ImageEngine is already a global CDN, there might be good reasons do this: You might already be using a CDN and would like to standardise, or you want specific security features specific CDNs can offer. 3rd party CDNs may also help you to keep traffic under control.

The trade-off is less optimized images. The reason for this is that ImageEngine can only optimize images so that the CDN in front is able to cache it efficiently and avoid cache pollution. By default ImageEngine will produce more versions of a single origin image than a CDN is able to cache.

However, if your plan supports it, ImageEngine will detect if a CDN is in front and adjust it's image optimization algorithm to fit the cache strategy of that specific CDN.

3rd party CDNs supported

If your plan supports 3rd party CDNs already, you don't have to do anything. ImageEngine will automatically detect and adjust. However, ImageEngine usually supports a slightly more sophisticated and effective integration in addition to the default behaviour.

Here you can find the integration details for the most common CDNs:

• Cloudflare
• Cloudfront
• Fastly
• Edgio
• Azure Front door
• Akamai

Note:

If you choose to use a CDN in front of ImageEngine, ImageEngine will be the origin of that CDN. This means that ImageEngine will only serve cache misses from the CDN. This makes some statistics and analytics misleading compared to the total traffic your images are generating. Moreover, some of the advanced settings for your engines, like browser cache time, may be overridden downstream.