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. 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.
Please use this thread to ask the related questions.
Topics help categorize Community content and increase your ability to discover relevant content.
@kautuk_sahni What features are provided in the inbuilt CDN with AEM cloud which is Fastly. Fastly isn't free, so want to understand if the client needs to pay for Fastly separately? How will pricing be structured for it?
The document starts with the “build-in CDN” statement, there’s no pricing implication beyond the license that the customer has already acquired. In other words, it’s part of the license by default.
Customers can’t opt-out default one. But they can add another CDN on top of ours. In which case they have to pay for this extra CDN of course.