Assets from Dynamic Media or AEM Assets don’t appear in Content Hub
Content Hub in AEM as a Cloud Service might not display assets from Dynamic Media or AEM Assets, even after publishing and approval. This typically happens due to missing CDN configuration or outdated asset approval status.
To fix this, update the CDN configuration, deploy changes to production, and reapprove affected assets.
Description description
Environment
- Adobe Experience Manager as a Cloud Service – Assets (Production)
Issue/Symptoms
- Assets from Dynamic Media or AEM Assets don’t show up in Content Hub, even though they have been published and approved.
- Followed guidance to set asset approval status to Approved, publish to Dynamic Media, and set approval target to Content Hub and/or Delivery. Despite this, the assets remain not visible in Content Hub.
Resolution resolution
Follow these steps to resolve the issue:
-
Update the CDN configuration to include the delivery domain for asset access:
code language-none - allOf: - reqProperty: method equals: OPTIONS - reqProperty: domain like: delivery-[ environment] -[ project] .adobeaemcloud.com -
Deploy the updated CDN configuration to the production environment.
-
For any previously approved assets that are still missing:
- Reject each affected asset in AEM Assets.
- Reapprove each asset so that it is processed with the new settings.
-
Confirm that all intended assets appear in Content Hub.
Note: If migrating multiple assets, provide top-level folder paths so a script can approve all assets under those folders while maintaining hierarchy and collection names.
Related reading
- Adobe Dynamic Media Classic Guide
- CDN in AEM as a Cloud Service in AEMaaCS User Guide