Adobe Managed CDN

The following steps illustrate how to use the Adobe Managed CDN (part of AEM Sites as a Cloud Service) to configure a property to deliver content from a site powered by Edge Delivery Services in Adobe Experience Manager Sites as a Cloud Service.

Prerequisites and limitations

You must have a license for Edge Delivery Services as part of Adobe Experience Manager Sites.
You must own the domain under which you want to serve your site.
You need to be able to make Domain Name System (DNS) changes to the domain name.
You have the choice to bring your own certificate or ask Adobe to provide one provisioned by Let’s Encrypt.
HTTPS is required and IPv6 is not supported.

Before you go live

There are two deployment options for going live with Adobe Managed CDN

Setup an HTTP proxy from an existing AEM Sites as a Cloud Service environment. This is typically used when you already have an existing environment and you want to migrate part of a site to Edge Delivery Services. You can also add a new environment.
Setup a new Edge Delivery site independently of an AEM Sites as a Cloud Service environment. This is the approach used when you do not have an AEM author or publish environment and you want to use Edge Delivery Services on its own. See here for benefits.

A checklist of the steps you need to do for both options:

Install or request a certificate in Cloud Manager (you need to do that for both www and non-www apex domains)
Install the domains Cloud Manager (you need to do that for both www and apex domains)
Add a CDN configuration to map your domain to your Edge Delivery site. (This will be done differently depending on what deployment option you chose)
Setup push invalidation in the project's configuration
Point the DNS CNAME of your www site to cdn.adobeaemcloud.com and the A records of your apex to the IP addresses listed below.

(Option 1) Setup a proxy from an existing environment

This requires an existing AEM Sites as a Cloud Service environment that needs to be configured via configuration pipeline to proxy some (or all) paths on your domain to your Edge Delivery Site. (see how to define a proxy using originSelectors and how to run a Configuration Pipeline).

A redirect from https://example.com to https://www.example.com must be defined using a redirect rule, but all other redirects may use the redirects spreadsheet

(Option 2) Setup an Edge Delivery site without an existing environment

In case you do not have an existing authoring/publish environment, follow the steps for setting up a new Edge Delivery site in Cloud Manager.

An automatic redirect will be established from https://example.com to https://www.example.com but all other redirects must happen through the redirects spreadsheet

Setup push invalidation

Push invalidation automatically purges content on the managed CDN whenever an author publishes content changes.

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

Push invalidation is enabled by adding specific properties to the project's configuration. Depending on how you author your content, this is done in two different ways:

If you author your content with Sharepoint or Google Docs, create an Excel workbook named .helix/config.xlsx in Sharepoint or a Google Sheet named .helix/config in Google Drive.
If you author your content with AEM Authoring and the Universal Editor, create a spreadsheet called configuration in the Sites console.
If your site is using the configuration service, see here how to update the CDN configuration.

In the spreadsheet, define the following configuration properties:

key	value	comment
`cdn.prod.host`	`<Production Host>`	Host name of production site, e.g. `www.example.com`
`cdn.prod.type`	`managed`
`cdn.prod.envId`	`<environment ID>`	optional (format: `pXXXX-eXXXX`)

After making changes to the configuration sheet, preview it with the Sidekick or publish it in the Sites console to activate the changes.

(Optional) Lower the TTL of existing DNS records before going live to enable a faster rollout

If the DNS records for your go-live domain have a long time-to-live (TTL)—such as 12 hours or more—you may want to temporarily lower the TTL (for example, to 1 hour or even 60 seconds) to speed up site rollout. Doing so ensures traffic is routed to the new site more quickly after launch. Be sure to restore the original TTL value when updating the DNS records for go-live.

As you go live

Make or request following DNS change:

For www.example.com set the CNAME DNS record to cdn.adobeaemcloud.com (see details).
Use a high time-to-live (TTL) value of 3600 seconds (one hour) or more to improve site reliability during a DNS outage. If you previously lowered the TTL for a faster go-live rollout, make sure to restore it to its original longer value.

If you want to establish an automatic redirect from https://example.com to https://www.example.com, the following additional steps are required

For example.com set the A record to these four IP addresses: 151.101.3.10, 151.101.67.10, 151.101.131.10, and 151.101.195.10 (see details)
If your DNS provider cannot support multiple IP addresses in an A record (for example, GoDaddy), use any of the listed IP addresses. This will be a bit less reliable.
Use the same high TTL as described above

Depending on your DNS setup—including the TTL specified in your DNS records—changes can take anywhere from a few minutes to several hours to propagate. If your site already receives traffic, ensure all redirects are configured or keep the existing site live until the TTL expires and all traffic is routed to the new site.

If you are hosting both the apex and www versions of the domain, make sure DNS is properly configured for both to enable certificate generation.

For a timed launch, consider setting up a temporary holding homepage that you can quickly replace with the final content at the launch time. Because publishing in AEM is fast and reliable, this approach gives you better control over when your content becomes publicly visible than relying solely on DNS changes.

After you go live

The AEM team reviews your setup and notifies you if any issues are found.