Push Invalidation for Adobe CDN?

[SaadAb]

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

[arunpatidar]

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-... 

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

[SaadAb]

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]

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.

[SaadAb]

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 

[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.

[SaadAb]

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

[arunpatidar]

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/con... 

[SaadAb]

So it seems its actually much simpler than this - considering we're just using an Adobe Managed CDN and pulling from our main branch the .live content of our EDS site. 

For clarity, our content is purged by URL and by cache tag/key.

According to other Adobe experts, all thats needed for an AMC is the following.
- Modifying the .config file in Sharepoint (in our case) and adding in cdn.prod.host and type. 

[kautuk_sahni]

@SaadAb Did you find the suggestions helpful? If you need more information, please let us know. If a response resolved your issue, kindly mark it as correct to help others in the future. Alternatively, if you discovered a solution on your own, we'd appreciate it if you could share it with the community. Thank you !

[konstantyn_diachenko]

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/con... . 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.