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

Push Invalidation for Adobe CDN?

  • April 1, 2025
  • 2 replies
  • 1320 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

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
Community Advisor
April 4, 2025

Thanks for some more clarity on this - but i guess an immediate follow up would naturally be; how would I know if 'manual clearing' will be necessary? 

And if cache expiry is the best method as its automated and passive, which documentation or steps outline it for EDS? There's a lot of varying information so want to be sure. Appreciate it. @arunpatidar 

 


Hi @saadab 

if 'manual clearing' will be necessary means your user expect updated content without waiting for automatic cache invalidation, which means you have some pages in your site where the TTL is longer than expected. However you would have upto date content on dispatcher because of OOTB flush agent.

 

For EDS, architecture is completely different, there is no dispatcher, the content is directly available at CDN hence you need some kind of cache invalidation mechanism if you are not caching content at Fastly but at your own CDN.

Arun Patidar
konstantyn_diachenko
Community 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.