According to what I see, is that you only have 800mb of heap space. Seems to me you did not pass Xms and Xmx parameters to your publish instance. A production instance needs more than 1gb ram. Give it some more breathing room. For example 4gb.

You can’t use remote paths. You must use local paths. To to do what you want to do, copy the full repository from box1 to box2 using for example scp or rsync to another location, like /data/source. Then run the crx2oak tool on box2 using /data/source as input and /opt/aem/crx-quickstart/repository/s...

Have you tried following the best practice as described in https://helpx.adobe.com/experience-manager/dispatcher/using/dispatcher-configuration.html#ConfiguringAccesstoContentfilter ?I mean, deny access to everything in your first filter rule, and then gradually allowing access to whatever is needed...

I would upgrade to the latest version of the AEM dispatcher first. See AEM Dispatcher Release Notes . If I remember correctly we had the same issue in an earlier version of the dispatcher. About the testing tools, there is The Dispatcher Security Checklist and the dispatcher health checks in Operati...

Just any value you want. It just needs to be the same  on all instances connected to that shared data store.

See the documentation at Hobbes.js Index. Don’t know if you still need write access to /apps though.

When you architect and implement your application, you know exactly which selectors you use, so it should not be rocket science to only allow those selectors in the dispatcher filter rules. The idea is to whitelist only what is needed. By default AEM allows for example to export your entire content ...

Do I need to mention your site should be on https?

Make sure your sslfilter is configured correctly if you are using ssl termination in the dispatcher or load balancer. See AEM redirecting user back to http if accessed through SSL terminated Load Balancer  for details. We experienced the same issue. When the sslfilter is set correctly, the cookie be...

Hi,Our company has also suffered from the same problem. We have a shared S3 bucket (1 author, 4 publishers) and when we started off, it was a little less than 1 TB in size, but over the time of a few weeks, it starting growing rapidly up to a whopping 5 TB (5x increase).It was indeed not in comparis...