Level 2

Question

Push Invalidation for Adobe CDN?

Forum|Forum|11 months ago
April 1, 2025
2 replies
1321 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.

arunpatidar

Community Advisor

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

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

Ok so I think i've been confusing EDS with AEM in regards to certain documented approaches to push invalidation, and wether Adobe CDN is its own thing or based on another CDN like fastly (as in, if its the same implementation process).

What im confirming now, is this - which was also brought up by Adobe Experts on a support chat:

- For Adobe Managed CDN (which is what my team is using for this project), and given the documentation on it (we did option #2, as it was a brand new creation, and we're using Cloud Manager EDS steps to map the new domain and what not for production); is this all I need to do?
- Also confirmed here
- Do i need to consider doing anything in the config-service or in cdn settings at all? Considering we don't have a repo-less setup.

Please confirm and ill consider this issue closed off and confirmed of an approach. Thank you for your time so far

Hi @saadab

What I understood from above that you are using AEMaaCS and relying on Adobe manage CDN. If thats true then

You have already configured the domains then you are ready to get served your content from AEM but also check below docs if case you need custom rules/setup

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/cdn-configuring-traffic

Arun Patidar

konstantyn_diachenko

Community Advisor

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.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded