DocumentationExperience Cloud KCS

CDN purge key access issues in AEM as a Cloud Service

Last update: July 16, 2026

CDN purge requests fail when the purge key is missing, outdated, invalid, or inaccessible. Verify the environment, validate the existing purge key, retrieve the correct purge key, and run an authenticated PURGE request to clear cached content successfully.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service (AEMaaCS)
  • Adobe Developer App Builder
  • AEM Assets Essentials

Issue/Symptoms

  • PURGE requests fail or return authorization errors.
  • Cache invalidation does not occur after a purge request.
  • Access to the purge key management interface is unavailable.
  • Cached content continues to be served after a purge attempt.

Cause

CDN purge keys are environment specific and can expire or be regenerated. When a purge request uses an outdated or incorrect key, CDN authentication fails and the purge request is rejected.

Resolution resolution

To resolve this issue, follow these steps:

  1. Identify the publish URL or CDN endpoint that requires cache invalidation.
  2. Verify whether the existing purge key is available and valid.
  3. Test the current purge key by sending a PURGE request against the affected resource.
  4. If the request fails, obtain a current purge key for the target environment.
  5. Use the updated purge key and retry the PURGE request.
  6. Verify that the resource reloads without using cached content.
  7. If required, perform a full purge or a surrogate-key purge based on your cache invalidation requirements.
  8. Contact Adobe Support if purge requests continue to fail after validating the purge key.
recommendation-more-help
experience-cloud-kcs-help-kbarticles