AEM Publish service has two primary caching layers, the AEMaaCS CDN and AEM Dispatcher. Assuming you don't have a custom CDN in front of the Cloud CDN, try the below steps- CDN - The AEM Publish CDN is TTL (time-to-live) based, meaning that the cache life is determined by the Cache-Control, Surrogat...

Hi @KarthickVe, Can you try implementing Interface ReplicationListener?    

Hi @amezcua1,   Is the issue with HTTPS access occurring only when you clear the cache and then access the site? If the cache is maintained then the HTTPS request are being served properly. Correct? The intent behind the question is to ensure your SSL/TLS configuration on the dispatcher server is co...

Hi @shafali12,    I have couple of inputs here -  1. Try using the following build command mvn clean install -PautoInstallPackage -Padobe-public Double check your settings.xml has the adobe-public profile in it - Reference How to set up the Adobe Maven Repository 2. Check your filter rules once to m...

Hi @KannanCh2,You can refer to the following document -  Configure an Azure Key Vault The general steps for integrating Azure Key Vault in AEMaaS would be as follow- Setup Azure Key Vault Key - Create new key vault instance, add secrets to the key vault & define access policies to read these secrets...

The jcr:read permission alone is enough for view privileges. Setting everyone to deny, with group1 and group2 set to allow for jcr:read on path /content/dam/organization/project1 should have worked!  Is it possible you have multiple permissions acting on "everyone" group? Can you share the permissio...

In AEMaaCS the usage of '/etc/designs' for storing design configurations has shifted. The design and client-side resources are now typically handled through the "/apps" and "/content" paths In AEMaaCS, "/etc/designs" is deprecated. Is there any particular reason why you are still housing images unde...

Hi @pixislinger, Yes this is the expected behavior. If you see the screenshot below you will see the coral-checkbox element listener acts on both the coral checkbox label and the actual checkbox.  Hope this helps!

When the AEM Dispatcher returns a 200 status code for secure pages, even though the AEM Publish instance correctly returns a 403 status code, it indicates that the Dispatcher might be serving cached content without properly checking authentication or authorization.   Can you try the below changes? 1...

Yes, by maintaining the Replication API as a facade, AEMaaCS allows a smooth transition in moving from traditional AEM deployments to the cloud service, ensuring that custom replication logic and integrations continue to function correctly.