Setup push invalidation for Adobe Managed 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.

Push invalidation is enabled by setting up the CDN section of the configuration service.

curl --request POST \
  --url https://admin.hlx.page/config/{org}/sites/{site}/cdn.json \
  --header 'content-type: application/json' \
  --data '{
	"prod": {
		"host": "{production host}",
		"type": "managed"
	}
}'

Configuration properties:

key	value	comment
host	<Production Host>	Host name of production site, e.g. www.yourdomain.com
type	managed

An optional envId property (format: pXXXX-eXXXX or or pXXXX-dXXXX) can be added if a large number of sites share the same repoless content origin. By setting a common envId, cache purge invalidations triggered by content changes are collapsed into a single purge request rather than firing separately for each site, improving efficiency and reducing redundant invalidation calls.

Note: The envId property is not needed for standard setups. and should be left unset in most cases. If you are unsure whether your setup requires it, contact Adobe.