Hi @rakesh_h2  Refer : https://www.linkedin.com/pulse/using-curl-aem-cloud-prince-shivhare  

Hi @rakesh_h2  Can you share the curl command which is not working in your case along with the error  .In cloud service we use domain name only for deletion or any other operation via cURL.   Thanks Himanshu

Hi @rakesh_h2 , IP port will not be available via cloud manager for AEM environment. For this specific requirement you can raise the support ticket . Also there will be multiple POD behind author and publish environment so check accordingly.   Thanks Himanshu

Hi @Yijun250211319mpv  Following below the observations.   Is there any possibility that a URL including "/ui#/" and "?appId=aemshell" is caused by other features instead of Unified Shell?   After disabling unified shell configuration it disappears as per my observation Is Unified Shell a configurat...

Also you can try to take git pull from adobe git and try to do sync manually from local git .    

Hi @Tanika02  After taking pull from your project git you can use the following commands  git remote add <remote-repo>git push <local_branch_name>:<desired_remote_branch_name>   Thanks Himanshu

HI @Asutosh_Jena_  We faced this for one of our config in AEM cloud instance (stage/Prod) and we tried the same . Also this was on one of the POD not on all PODs . For more details check https://issues.apache.org/jira/browse/SLING-11855   Thanks Himanshu

Hi @Asutosh_Jena_    Kindly rename your config from  org.apache.sling.caconfig.impl.override.OsgiConfigurationOverrideProvider~pdf-viewer.cfg.json   to org.apache.sling.caconfig.impl.override.OsgiConfigurationOverrideProvider-pdf-viewer.cfg.json   replace~ with- in your config name .   Thanks Himan...

Hi @Uppari_Ramesh  You can create a user group and add the allowed users for replication for security . Secondly you can add a check on quick publish and manage replication via custom JS to check the property from the metadata schema field .   Thanks Himanshu

Hi Rohan, Following below my observations regarding the scenario you mentioned. 1.Every user group is assigned to one of the product profile . As soon you assign the user to that group user will be able to access that product . Also you cannot remove that product profile from the user if user is ass...