Isolating non-production and production environments in AEM Dynamic Media
When non-production and production environments share one Dynamic Media company, asset changes in non-production can affect production. Request a separate non-production company to keep the environments isolated.
Description description
Organizations using AEM Dynamic Media may have both non-production (such as development or user acceptance testing) and production environments configured to use the same Dynamic Media company. In this setup, all environments share a single image repository. As a result, publishing, unpublishing, or deleting an asset in a non-production environment can directly impact assets in production. This lack of isolation can lead to unintended changes in production assets during testing or development, potentially disrupting workflows and asset integrity.
Environment
Adobe Experience Manager (AEM) Dynamic Media (all versions)
Symptoms
- Publishing or unpublishing an asset in a non-production environment changes the asset state in production.
- Environments are not separated, which can lead to accidental changes in production during testing.
Cause
Using a single Dynamic Media company for both production and non-production environments causes shared asset repositories, resulting in cross-environment changes.
Resolution resolution
Follow these steps to resolve the issue.
-
Submit a support request to Adobe to provision a separate non-production Dynamic Media company for your lower environments (such as development or testing). In your request, include:
- The desired company name for non-production (use a generic name reflecting its purpose).
- The name of your existing production company.
- The purpose (for non-production use only).
- The region (should match your production company).
- Delivery domain requirements (default Adobe delivery domain unless a vanity domain is needed).
-
Adobe Support will provision the new non-production company and provide administrator credentials.
-
Once you receive the credentials, confirm access to the new company and assign administrators.
-
Update the Dynamic Media cloud configuration in your AEM non-production environments to use the new company credentials and endpoints provided by Adobe. Ensure your production environment continues to use the original production company.
-
The new non-production company will start empty by default. Upload or sync only the assets you need for non-production testing.
-
Verify that asset changes in non-production no longer impact production assets.