Last I checked months back, Vanity urls used to work well in AEM CS environments. Have you replicated the behavior on your dispatcher SDK running locally? I would suggest to enable debug logging for dispatcher module and the rewrite engine to surface the real problem. Below are the logs captured for...

The geolocation headers are coming from CDN to the origin.  The flow should be something like request -> cdn -> (cdn appends headers) -> dispatcher -> aem so one needs to fetch it on apache and redirect or do  things. If the headers are not visible in the flow(you need to explicitly log it to see th...

Have tried to rely on repoinit scripts to assign ACL for these paths ?Repoinit scripts might help set the correct permissions and is the best practice.

For customer environments, Stage+Production environment are auto-updated with latest releases. For every release that Adobe pushes, There is a strict testing regime where the release is tested on many customer environments to avoid any regressions. These tests include functional, UI variance and oth...

There is no specific setting needed on Cloud Manager front. Can you replicate this issue on your local dispatcher sdk setup ? Also, Switch on the debug logs for dispatcher + trace level logging for the rewrite engine so it surfaces whats actually happening on your dispatcher module and creating this...

Can you replicate this issue on your local dispatcher sdk setup ? Also, Switch on the debug logs for dispatcher + trace level logging for the rewrite engine so it surfaces whats actually happening on your dispatcher module and creating this problem Share the debug logs if you can here

Hi, What's the AEM SDK version you are using? Also, Java version plays a big role here. Download the latest AEM sdk along with Java 11 to  start the AEM local runtime.  For all the setup requirements, Review [1] [1] : https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/loc...

Currently the maintenance tasks can't be monitored similar to the Operations dashboard in previous AEM versions. It's possible that these could be surfaced in the future either on the Developer console or Cloud Manager UI. Also, You shouldn't be worried about the purge tasks(audit, workflow) as the ...

which index files do you delete? under /crx-quickstart/repository? This shouldn't be the case unless there is some corruption in the repository or aem is not started with the correct permissions.  I would suggest to review the error logs at the time of startup to understand if you see any repository...

You can't use Asset compute service in local AEM SDK. It still works using the legacy DAM update asset workflow. You can extend and use processing profiles  once you have prerequisites like AEM as a Cloud ServiceAdobe Project FireFlyCloud storageAzure Blob Storageor Amazon S3