How to Use a Custom CDN in AEM as a Cloud and Restrict Fastly CDN | Community
Skip to main content
K
KannanCh2
Level 2
May 18, 2024
Solved

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

  • May 18, 2024
  • 6 replies
  • 2265 views

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

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by AMANATH_ULLAH

@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/content-delivery/caching

6 replies

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
May 18, 2024

Check the documentation at https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/cdn#point-to-point-CDN

    gkalyan
    Community Advisor and Adobe Champion
    gkalyanCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    May 18, 2024

    @kannanch2 

    +1 on @joerghoh 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

      AMANATH_ULLAH
      Community Advisor
      AMANATH_ULLAHCommunity AdvisorAccepted solution
      Community Advisor
      May 19, 2024

      @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/content-delivery/caching

      Amanath Ullah
        aanchal-sikka
        Community Advisor
        aanchal-sikkaCommunity Advisor
        Community Advisor
        May 19, 2024

        @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 @joerghoh 

        Aanchal Sikka
          kautuk_sahni
          Community Manager
          kautuk_sahniCommunity Manager
          Community Manager
          May 20, 2024

          @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
          EstebanBustamante
          Community Advisor and Adobe Champion
          EstebanBustamanteCommunity Advisor and Adobe Champion
          Community Advisor and Adobe Champion
          May 20, 2024

          @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
            Terms & ConditionsAccessibility statement

            Loading footer...