Hi,   Running the revision cleanup (aka online compaction, see https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/deploying/revision-cleanup)  periodically should be able to keep the growth of the repository itself (the TarMK) managable, as "overwritten" ...

And just as a general statement: AEM making requests to itself is in general considered a code smell. There should always be a direct way (using API) to achieve the same.   (And it case it is not, there should be one... please raise a feature request for it.)

thanks, it's much clearer now.

Why do you use Content Distribution to replicate content from author to publish? Isn't it possible for you to use the Replication API for that?  

And in case of AEM CS you can also use the Traffic Rules to ratelimit and/or block such requests. Check the documentation on Traffic Rules at https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/security/traffic-filter-rules-including-waf

You can lock a page, and that should prevent it from being modified by someone else.    Normally saves are not done on a page level (except for page properties), but only on component level, that means that multiple changes can happen and not cause issues. But the usual recommendation is to ensure b...

I guess that the biggest issue will have is the consolidation of multiple applications; I think that the technical constraints are solveable, but the bigger one will the management aspect:   * Consolidate multiple development teams * each of them operating under different constraints (e.g. budget, f...

Please fill a support ticket, and provide relevant information like timing and how you experienced the slowness and the downtime.   Also, status.adobe.com reflects in general issues affecting the service "AEM as a Cloud Service" as an overall service. It does not necessarily reflect the status of in...

in Stage and PROD you cannot do that, as the same immutable content image is used for both. That means you need some runtime logic which achieves that.  (My question would be why this is even necessary ... I could imagine some cases, but have barely seen any really convincing case ...)

Can you please provide any rationale for this feature? What is the expected change when this checkbox is checked? Why do you want to move the binary to a cold-storage instead of the regular storage? For cost reasons?What would be the impact when the asset was moved to cold-storage? Would it still be...