DocumentationExperience Cloud KCS

Maintain increased pod capacity during high-traffic campaigns in AEM as a Cloud Service

Last update: October 26, 2026

Adobe Experience Manager (AEM) as a Cloud Service (AEMaaCS) may require elevated publish and Dispatcher pod capacity to handle anticipated traffic spikes during major campaigns and prevent downtime or performance issues. To resolve the issue, review the current scaling configuration, confirm that elevated limits remain in place during the campaign, monitor traffic and autoscaling, and request further adjustments if needed.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS)

Issue/Symptoms

  • Increased publish and Dispatcher pod capacity may be required to handle anticipated web traffic during major campaigns.
  • There is concern about whether increased pod capacity will remain active during a high-traffic campaign period.
  • Reducing pod capacity prematurely may cause downtime or performance issues during critical business events.

Root cause

Elevated pod capacity and autoscaling limits are necessary to absorb anticipated traffic spikes during major campaigns and prevent downtime or performance issues.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Review the current pod scaling configuration:

    • Confirm the current autoscaling parameters, including the minimum and maximum number of publish and Dispatcher pods and CPU and memory limits.
    • Example configuration for the Publish tier per pod: CPU: minimum 1 vCPU, maximum 10 vCPU; memory: 14 GiB; replicas: minimum 6, maximum 12.

  2. Confirm that increased autoscaling limits remain in place:

    • Coordinate with the internal DevOps team to ensure that the elevated autoscaling limits and pod capacity remain active for the duration of the campaign window.
    • If you rely on external support for configuration changes, confirm that no changes are planned to reduce these limits before or during the campaign period.

  3. Monitor traffic and autoscaling behavior:

    • Use available monitoring tools to track traffic metrics and autoscaling behavior during the campaign and confirm that the environment scales as expected.
    • If actual traffic exceeds previous estimates, be prepared to request further increases in pod limits.

  4. Communicate changes in expected traffic:

    • If you anticipate higher traffic than during previous events, gather updated metrics such as peak visits per minute, peak requests per second (RPS), and expected concurrency.
    • Share these metrics with the internal DevOps team or external support to reassess scaling needs.

  5. If additional scaling is required, initiate a new configuration change request with updated traffic projections and business requirements.

  6. During and after the campaign period, monitor system performance and autoscaling activity to confirm that the elevated pod limits remain in effect and meet the required capacity.

recommendation-more-help
experience-cloud-kcs-help-kbarticles