AEM Cloud Service Autoscaling and Customer Control for Lower Environments

[MatthewDa19]

In AEM as a Cloud Service (AEMaaCS), is there an automatic mechanism that scales down or optimizes resource usage during periods of low activity (for example, nights or weekends) for non-production environments? If so, can customers configure these scaling rules themselves, or is it entirely managed by Adobe?

[SantoshSai · Accepted solution]

Hi @MatthewDa19,

As far as I understand, on Cloud, Adobe manages scaling automatically based on real-time system load and usage. This ensures environments like Author and Publish scale up during high demand and scale down during low demand. Customers cannot manually configure scaling rules - it's fully controlled by Adobe's infrastructure.
For non-production environments, while autoscaling exists to some extent, manual hibernation or aggressive scaling for cost-saving, I don't think so it is user-configurable.

Please let me know if I'm wrong or if anyone has more details to share! I'm open to learning more.

[muskaanchandwani]

Hello @MatthewDa19 
AEMaaCS is always at scale and the infrastructure is managed by Adobe.

It is based on the use of orchestration engine, that constantly monitors the state of the service, and dynamically scales each of the service instance as per the actual need, both scaling up and down.
This is true for the number of nodes, the amount of memory and the allocated CPU capacity on each node.

Official Documentation Reference:
https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/introduction/what-...

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/overview/introdu...

[ShivamKumar]

HI @MatthewDa19 ,

Accoding to my understanding, Adobe’s mechanism optimizes resource usage, particularly for non-production environments (such as development, stage, QA) in AEMaaCS. Adobe automatically monitors server load, traffic, and activity. During periods of low activity or extended inactivity Adobe may suspend or scale down these environments to conserve resources and reduce costs. When users start accessing these environments again, the environments automatically resume and scale back up to serve the workload without any manual intervention.

Customers cannot manually configure these scaling policies. Customers only manage content, code, and configuration at the application level (like Sites, Assets, Experience Fragments) — not infrastructure scaling.

Thanks.