AEM as Cloud Service is shipped with a built-in CDN. It’s main purpose is to reduce latency by delivering cacheable content from the CDN nodes at the edge, near the browser. It is fully managed and configured for optimal performance of AEM applications.
The AEM managed CDN will satisfy most customer’s performance and security requirements. For the publish tier, customers can optionally point to it from their own CDN, which they will need to manage. This will be allowed on a case-by-case basis, based on meeting certain pre-requisites including, but not limited to, the customer having a legacy integration with their CDN vendor that is difficult to abandon.
Follow the sections below to use Cloud Manager self-service UI to prepare for content delivery by using Adobe’s out-of-the-box CDN:
By default, for an Adobe Managed CDN setup, all public traffic can make its way to the publish service, for both production and non-production (development and stage) environments. If you wish to limit traffic to the publish service for a given environment (for example, limiting staging by a range of IP addresses) you can do this in a self-service way via Cloud Manager UI.
Refer to Managing IP Allow Lists to learn more.
If a customer must use its existing CDN, they may manage it and point it to Adobe’s managed CDN, providing the following are satisfied:
X-Forwarded-Hostheader with the domain name.
X-Edge-Key, which is needed to route traffic correctly to the AEM servers. The value should come from Adobe.
Prior to accepting live traffic, you should validate with Adobe customer support that the end-to-end traffic routing is functioning correctly.
There is potentially a small performance hit due to the extra hop, although hops from the customer CDN to Adobe’s managed CDN are likely to be efficient.
Note that this customer CDN configuration is supported for the publish tier, but not in front of the author tier.