For Issue 1, you might want to disable the ssl - you can try building only the ui.frontend module after configuring via "git config --global http.sslVerify false" This will disable SSL certificate checking for the repo.    

Hi @jayv25585659,   You can create symlinks on windows -  Syntax — mklink <link> <target> Reference Link - Validating Dispatcher Files   Hope this helps! Rohan Garg

This happens when the corporate network is replacing all SSL certificates with their own. These certs are not trusted by default. As a workaround, run mvn clean package -U -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true -Dmaven.wagon.http.ssl.ignore.validity.dates=true

Hi @Rama_KrishnaNy,   With respect to EDS, AEM is an on origin service that you can plug into your existing CDN   There are 4 layers to the overall composable architecture -  CDN, DNS, TLS certificates etc. which are customer specific infrastructureAdobe's Edge Compute Layer Adobe's Storage Layer ...

Adding few more blogs and references besides the above mentioned official documentation pages which make up for an interesting read -  @Imran__Khan's  blog Dispatcher Setup AEM as a Cloud Service@Jörg_Hoh's blog Limits of dispatcher caching with AEM as a Cloud ServiceDispatcher in the Cloud   Hope t...

Hi @SvenDev, You can refer to the article - How to track down unexpected OSGi configuration updates   Hope this helps!

Hi @SwetaB,  There is an excellent blog on this - please refer Multi Tenancy with Adobe Cloud Manager It talks about 3 deployment models -  Model 1 - Using Multiple RepositoriesHere Adobe explains how we can sync customer managed Git repositories with CM repos by making use of Git actions and CI job...

Hi @georhe6,    There is an excellent blog on this - please refer Multi Tenancy with Adobe Cloud Manager It talks about 3 deployment models -  Model 1 - Using Multiple RepositoriesHere Adobe explains how we can sync customer managed Git repositories with CM repos by making use of Git actions and CI ...

Hi @ElvisRo,   Couple of suggestions here -  Manually delete the npm and node folders in .m2\repository\com\github\eirslett\ and then re-run the buildCould you replace the .tar.gz file with a .exe file? (for windows) The issue is with the extracting the archive. Replacing the archive with executable...

Hi @SushmaNa,   Couple of checkpoints for this -  1. Check whether the dispatcher is able to filter and allow request forward to publish  # /005 { /type "allow" /url "/bin/*" } # allow bin path access Also try to bind your servlet to resource type and not path if possible. You can refer to the...