Configure a custom domain for Dynamic Media CDN in AEM 6.5

This article describes how to configure a custom domain for serving assets from Dynamic Media in Adobe Experience Manager (AEM) 6.5, including identifying the correct CDN endpoint and managing SSL certificates.

Description description

When using Dynamic Media with AEM 6.5, organizations may want to serve assets from a custom domain instead of the default Dynamic Media CDN endpoint. This requires identifying the correct CDN endpoint and configuring DNS and SSL settings.

Environment

Adobe Experience Manager (AEM) 6.5 with Dynamic Media enabled

Symptoms

  • Need to serve assets from a custom domain via Dynamic Media
  • Need to determine the correct CDN endpoint for DNS configuration

Cause

Mapping a custom domain to Dynamic Media requires pointing the domain to the correct CDN endpoint and ensuring SSL is properly configured if HTTPS is needed.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Ensure that Dynamic Media is enabled and properly configured in your AEM 6.5 environment.

  2. In AEM, navigate to Tools > Assets > Dynamic Media Configuration.

  3. Locate the Base URL or CDN endpoint provided for asset delivery. This is the target for your custom domain CNAME record.

  4. In your DNS provider’s management console, create a CNAME record for your custom domain that points to the Dynamic Media CDN endpoint URL identified in step 3.

  5. If you require SSL (HTTPS) for your custom domain:

    • Provision an SSL certificate for your custom domain.

    • SSL certificates can typically be managed through your CDN provider or, if using Adobe-provided CDN, by contacting Dynamic Media support to request certificate mapping.

  6. After DNS and SSL configuration, validate asset delivery by accessing assets through your custom domain and confirming they’re served correctly from Dynamic Media.

Troubleshooting tips:

  • If assets aren’t loading via the custom domain, verify that the CNAME record is correctly set and DNS changes have propagated.
  • Ensure the correct CDN endpoint is used and matches the environment (production, staging, etc.).
  • For SSL issues, confirm that the certificate is valid and correctly mapped to the custom domain.
recommendation-more-help
experience-cloud-kcs-help-kbarticles