--- title: "Dynamic Media Custom Domains" path: https://www.eonshowroom.eon.com/en/aem-basics/dynamic-media-custom-domains.html lastModified: 2026-09-10T06:43:37.854Z --- # Dynamic Media Custom Domains # Custom Domains for Dynamic Media Assets ###### Why use your own domain? ### Default Dynamic Media URLs If you click on one of your published images and open it in a new browser tab, you will likely find that the domain in the URL is not the domain of your website, but instead looks something like this: [https://s7g10.scene7.com/](https://s7g10.scene7.com/).... This is the default domain used for assets published to Adobe Dynamic Media. Once an asset has been published to Dynamic Media, it is no longer served directly from AEM. Instead, the asset is delivered through **Adobe’s asset CDN**, which provides the performance and scalability required to serve images and videos efficiently. ###### Why this may not be desirable While this setup works out of the box, using the scene7.com domain for your assets may not be desirable from a branding, ownership and SEO perspective. Ideally, assets such as images and videos should be served under the same domain as the website on which they are used. This creates a more consistent and coherent URL structure and ensures that the asset URLs are associated with your own domain rather than with Adobe’s infrastructure. In this how-to, we will show you how to configure your setup so that Dynamic Media assets are still delivered through Adobe’s CDN, but are accessed using **your own website domain/cdm-assets**. ###### Main benefits: - Assets are accessed using your own website domain. - URLs are more consistent from a branding and ownership perspective. - Dynamic Media continues to provide the underlying CDN delivery. - The setup supports a more coherent URL structure for SEO. ![Image shows how to open a picture in a new browser tab](https://www.eonshowroom.eon.com/cdm-assets/is/image/eon/openimage%3A2-1?qlt=50&fmt=webp-alpha&ts=1787910269155) ![Image shows that the domain of the image is scene7.com instead of an E.ON one.](https://www.eonshowroom.eon.com/cdm-assets/is/image/eon/Screenshot%202026-08-28%20at%2011.03.56%3A2-1?qlt=50&fmt=webp-alpha&ts=1787909715533) ### Configuration ###### Configuration in a nutshell The setup consists of two steps: - **Submit an AEMPS ticket** for implementation of the required CDN configuration. - **Enable the feature in the respective Context-Aware Configuration (CAConfig).** ## Step 1 – Submit an AEMPS ticket ###### Request the required CDN configuration The prerequisite for step 2 is to submit an AEMPS ticket to let the operations team know about your request. Technically, this feature is implemented using origin rewrites within our CDN provider. Therefore, our team needs to implement a snippet that takes care of this, and your ticket will let them know what needs to be done. ###### Clone the existing ticket Please open the following link to the relevant ticket and clone it: [https://jira.eon.com/browse/AEMPS-1119](https://jira.eon.com/browse/AEMPS-1119) In the cloned ticket's description, follow the instructions highlighted in red. ###### Wait for implementation Within the next two or three days, our operations team will pick up the ticket and implement the required changes. Please check your emails regularly for updates. Once the ticket has been handed over to you for testing, please proceed with step 2. ## Step 2 – Enable the feature in CAConfig ###### Open the relevant CAConfig When the AEMPS ticket has been set to *done,* we are ready to continue. You can now activate or deactivate the feature at any time. To do so, you need to find the respective Context-Aware Configuration (CAConfig). If you want the feature to be enabled for your entire site, you should select the topmost CAConfig. However, you can also activate the feature for a particular section of your website. In that case, you need to find or create a CAConfig for that specific area. ###### Enable the Dynamic Media setting Open the CAConfig and search for the "**FoundationNg Site Config**". Click it to open and search for the entry "**Use Dispatcher URL for Dynamic Media Assets (SEO)**". If step 1 has been completed correctly, you can now enable the checkbox and publish the CAConfig. Give it about a minute to make sure the publication workflow has finished. Delete your cache, check an image on a page where the CAConfig is active and verify whether it is now being served under your domain instead of the *Scene7* domain. ###### Verify the result If so, you're done. Congratulations 🎉. Don't forget to close the ticket you have opened in step 1. **If not, please double-check:** - that the domain specified in the AEMPS ticket matches the domain you are testing. - That the published CAConfig applies to the page you are testing. If both look correct, please use the ticket from step 1 to ask someone from our team to investigate the issue. Kindly share the link to your config file within the comments. ## Disclaimer There is a very tiny chance that the identifier (cdm-assets) we use to perform the origin rewrite could clash with a specific content path. Before submitting the ticket please verify that you do not serve any content at or below this path: https://yourdomain.tld/cdm-assets where *yourdomain.tld* is the domain under which your website is served. ## FAQ **It does not work on our DEV and STAGE environment. Why?** It could be done, but it would require additional effort due to the zone structure of our CDN. If you absolutely require this, please open another ticket and explicitly request it. However, there is little benefit in doing so, as this feature is intended for public websites only. **How does the origin rewriting work?** AEM renders assets with your website's domain instead of the original *scene7* domain and adds an identifier ("cdm-assets") right after the domain that our CDN listens for. **DM default Url**: https://scene7.com/myimage.jpg **turns to**: https://www.eon.com/cdm-assets/myimage.jpg When that suffix is detected it just inverts the process, i.e. it replaces the entire domain including the suffix with the original scene7 domain. For that reason make sure that the "cdm-assets" suffix is not used within your website. **Is there a performance impact due to the rewriting?** Yes, there is an impact because there is another hop in the route. This is negligible and not detectable within the naturally varying response times of the network itself.