BYO CDN Setup for hlx.live
NOTE: The instructions linked on this page apply to the previous version of Edge Delivery Services and are provided for customers who have not upgraded to aem.live yet. The current version of this document is provided here.
Customers may use their own CDN to deliver AEM content under their own domain (aka BYO Production CDN). While customers are generally free to configure their CDN according to their own needs there are some settings mandated/recommended by Adobe Experience Manager:
- Origin url
https://main--<yoursite>--<yourorg>.hlx.live
- Headers sent to origin
X-Forwarded-Host: <production domain>
X-Push-Invalidation: enabled
(optional, see Configuring Push Invalidation)
- Origin cache control
I.e. Cache TTL on the production CDN is controlled via origin cache control response headers. This should be enabled (if available). - Compression (gzip)
Should be enabled - Query parameters
- Must be forwarded to origin
- Must be included in cache key
Age
response header
TheAge
response header must be either suppressed or overridden (Age: 0
)
Vendor-specific setup instructions
If you already have a CDN, follow the instructions below. If you are not sure which CDN to pick, follow our guide to CDN selection.
Cloudflare Worker Setup
Learn how to configure Cloudflare to deliver content.
Akamai Setup
Discover how to use the Akamai Property Manager to configure a property to deliver content
Fastly Setup
This guide illustrates how to configure Fastly to deliver content.
CloudFront Setup
Set up Amazon Web Services Cloudfront to deliver your AEM site with push invalidation
Bring your own DNS
A custom domain without having to set up a content delivery network.
IMPORTANT: The production CDN setup should be validated and tested in a stage environment prior to going public.