Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

How to Use a Custom CDN in AEM as a Cloud and Restrict Fastly CDN

Avatar

Level 3

Hi All

 

In AEM as a Cloud Service, Fastly is provided as the out-of-the-box CDN. However, if a client prefers to use their own CDN , So How to restrict the OOTB CDN .anyone suggest any relevant documents or details pls .

 

Thanks

1 Accepted Solution

Avatar

Correct answer by
Level 6

@KannanCh2 The default HTML/Text caching setting can be disabled by defining the DISABLE_DEFAULT_CACHING variable in global.vars
Define DISABLE_DEFAULT_CACHING

 

The Surrogate-Control header applies to the Adobe managed CDN. We can use this header and set it based on our requirements

 

<LocationMatch "^/content/.*\.(html)$">
     Header set Surrogate-Control "max-age=3600"
     Header set Age 0
</LocationMatch>

 

Refer to below link 

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/con...

View solution in original post

6 Replies

Avatar

Level 9

@KannanCh2 

+1 on @Jörg_Hoh documentation

 

Here is a documentation on picking the right CDN

https://www.aem.live/docs/cdn-guide

 

Here is another documentation for BYO CDN setup

https://www.aem.live/docs/byo-cdn-setup

Avatar

Correct answer by
Level 6

@KannanCh2 The default HTML/Text caching setting can be disabled by defining the DISABLE_DEFAULT_CACHING variable in global.vars
Define DISABLE_DEFAULT_CACHING

 

The Surrogate-Control header applies to the Adobe managed CDN. We can use this header and set it based on our requirements

 

<LocationMatch "^/content/.*\.(html)$">
     Header set Surrogate-Control "max-age=3600"
     Header set Age 0
</LocationMatch>

 

Refer to below link 

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/con...

Avatar

Community Advisor

@KannanCh2 

 

You might have to check with Adobe on bypassing Adobe CDN. Recommendation might be to point Customer CDN to Adobe-managed CDN.

 

Many caching rules are taken care of by-default (example assets). The moment we use "DISABLE_DEFAULT_CACHING", we might have more-work at hand to fine-tune the cache.

 

I would request you to raise an Adobe ticket for clarifications after going through the documentation shared by @Jörg_Hoh 


Aanchal Sikka

Avatar

Administrator

@KannanCh2 Did you find the suggestion helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.



Kautuk Sahni

Avatar

Community Advisor

@KannanCh2 

 

If you are asking if you can get rid of Adobe's CDN, the short answer is NO. This is part of the Architecture of AEMaaCS, you can bring your own CDN and add it on top of Adobe's CDN but it is not really a swap nor a replace.

Hope this helps



Esteban Bustamante