In theory and for AEM on-premise (and potentially AMS), it should be possible to use these tools to sync content from one publish instance to another. For AEM CS, this is not possible (but most of the tools won't apply here at all).

In general, it is not a recommended practice to sync content between publishers. There are various challenges that arise with this kind of approach. In the past, AEMs approach was to pull changes that had been applied to one publisher (for user generated content, e. g. user comments, ratings and the like) back to the authoring system via reverse replication and the publish/propagate them to all publish instances (see also this article). This practice is no longer recommended and would not even work for AEM CS.

To guide towards a proper solution, it would be helpful to share some background and the underlying business requirement.

Hi @anas_r!

The error message clearly mentions an HTTP 401 Unauthorized status code when the tool is trying to access your Cloud Service environment.

There are different things to try to get to the root cause:

• Please double check on the credentials provided as well as permissions granted for the account you are using for the content sync. Have you tried a manual login with these credentials? Have you tried accessing the path mentioned in the error message via browser?
• Have you checked the log files on the instance where the sync tool is running for additional information? Are there other errors, stack traces of relevant log messages to be found that can help to guide you to the root cause?
• Have you also checked the log files (including access.log and request.log) on the target Cloud instance?

Hope this helps!