Push Invalidation for Adobe CDN? | Community
Skip to main content
S
SaadAb
Level 2
April 1, 2025
Question

Push Invalidation for Adobe CDN?

  • April 1, 2025
  • 2 replies
  • 1296 views

Hey Team,

 

I've read in the documentation that Push Invalidation (a crucial piece of the content pipeline), is not available for the Adobe Managed CDN and only for BYOCDN's like Cloudflare, Fastly, Akamai, and CloudFront. 

 

If this is the case, how then would i enable or manage push invalidation or auto-content purging for published content on the production site post-golive? Since we are using the Adobe CDN. 

 

On other notes, I've read that the Adobe CDN is actually Fastly based so Push invalidation could work? Please clarify this as the docs don't support that point outright.

 

Thanks

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

2 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
April 1, 2025

Hi @saadab 

Please check

https://aemtechblog.medium.com/cdn-cache-invalidation-in-aemaacs-fa389baca8e4 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/invalidate-dispatcher-and-cdn-cache-on-aem-cloud/m-p/635209 

https://medium.com/@giuseppebaglio/automating-cdn-cache-invalidation-in-aem-d419b538c8ea 

Arun Patidar
    S
    SaadAbAuthor
    Level 2
    April 2, 2025

    Thanks for this - just wondering what your reccommended best approach would be then? And my initial confusion was in fact wether Fastly was what Adobe CDN is based on, as it was in separate category as the others in the documentation. 

    Can you confirm if this documentation is applicable for EDS on AEMaaCS? https://www.aem.live/docs/byo-cdn-fastly-setup.

    Because if so, why not just refer to it? 

    Some clarity would be great, as there seems to be multiple approaches to this (some adobe approved and some not, and id rather stick to a documented one)

    arunpatidar
    Community Advisor
    arunpatidarCommunity Advisor
    Community Advisor
    April 3, 2025

    Hi @saadab 

    The ideal approach is to rely on cache expiry rather than manually clearing the CDN cache. If manual clearing is necessary, it's a sign that the TTL settings need to be reviewed. 

    However, if you must purge the cache, using APIs is the recommended method.

    Please check https://cqdump.joerghoh.de/category/cdn/ from @joerghoh 

     

    Yes,  https://www.aem.live/docs/byo-cdn-fastly-setup. is applicable only for EDS setup.

    Arun Patidar
      konstantyn_diachenko
      Community Advisor
      konstantyn_diachenkoCommunity Advisor
      Community Advisor
      April 1, 2025

      Hi @saadab ,

       

      You linked documentation for Edge Delivery Services. However, if you are looking for CDN cache purge opportunities, you can read this documentation: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/cdn-cache-purge . AEMaaCS provides an ability to purge Adobe CDN cache. AEM as a Cloud Service allows you to configure a Purge API Token, which can then be used in Purge API calls. Read Configuring CDN Credentials and Authentication to learn how to configure this token using the Cloud Manager Config Pipeline Authentication directives.

       

      Best regards,

      Kostiantyn Diachenko.

      Kostiantyn Diachenko, Community Advisor, Certified Senior AEM Developer, creator of free AEM VLT Tool, maintainer of AEM Tools plugin.
        Terms & ConditionsAccessibility statement

        Loading footer...