Configuring push invalidation for BYO production CDN

Push invalidation automatically purges content on the customer's production CDN (e.g. www.yourdomain.com) whenever content or code changes are made on AEM origins with the main branch in the host name (e.g. main--site--org.aem.live). Changes pushed to other origins do not trigger push invalidation.

Content is purged by URL and by cache tag/key.

Setting up push invalidation requires 2 steps:

• Configuration
• Opt-In Request Header

Configuration

Push invalidation is currently supported for CDNs of the following vendors:

• Fastly
• Akamai
• Cloudflare
• CloudFront
• Adobe Managed

Push invalidation is enabled by setting the project's production CDN configuration. The following sections describe the vendor-specific properties required to set up push invalidation.

Opt-In Request Header

The production CDN needs to send the following opt-in header to the origin in order to enable long cache TTLs:

X-Push-Invalidation: enabled