DocumentationExperience Cloud KCS

Custom cq:AuditEvent index not deployed in Adobe Experience Manager as a Cloud Service

Last update: October 30, 2026

In Adobe Experience Manager as a Cloud Service, a custom Oak index targeting cq:AuditEvent appears in the local SDK but doesn’t appear in the Cloud Service environment after deployment. To fix this issue, follow the required naming convention for fully custom indexes.

Description description

Environment

Adobe Experience Manager as a Cloud Service (all versions)

Issue/Symptoms

  • A custom Oak index targeting cq:AuditEvent, such as /var/audit or /var/audit/com.day.cq.replication, is packaged and deployed through Cloud Manager.
  • The index node appears in /oak:index on the local AEM as a Cloud Service SDK but doesn’t appear in /oak:index on the Cloud Service environment after deployment.
  • Other custom content indexes from the same package are deployed and work as expected.
  • The custom index is defined as a standalone oak:QueryIndexDefinition in a content package, registered in filter.xml, and matches the ACS AEM Commons “Audit Log Search” documentation specification.
  • The issue affects indexes targeting cq:AuditEvent under /var/audit.
  • No error is reported during deployment, but the index is missing in the Cloud Service environment.

Cause

Cloud Manager ignores custom Oak indexes that don’t follow the required naming convention for fully custom indexes. As a result, the index isn’t deployed to AEM as a Cloud Service environments, even though it appears in local SDKs.

Resolution resolution

Follow the steps below to resolve the issue.

  1. Review the custom index name:

    1. Ensure your custom Oak index name follows the required AEM as a Cloud Service naming convention for fully custom indexes.
    2. The format should be .<index-name>-custom-<number>.
    3. Example: exampleReplicationAuditLucene-1-custom-1

  2. Update the index definition:

    1. Rename your index node in the content package to match the required naming convention.
    2. Update all references in your package files, such as filter.xml and node definitions.

  3. Redeploy via Cloud Manager:

    1. Deploy the updated package through your standard Cloud Manager pipeline.
    2. After deployment, verify that the custom index appears in /oak:index on the Cloud Service environment.

  4. Confirm that queries against /var/audit or /var/audit/com.day.cq.replication now use the custom index as intended.

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