Documentation

Published assets return 404 on Edge Delivery Services (AEMaaCS)

Last update: Mon Sep 08 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

If your published assets return 404 (Not Found) errors on Edge Delivery Services, check your config.json file. You must include the correct content paths and assign the appropriate cloud configuration to the DAM folder.

Description description

Environment

  • Adobe Experience Manager (AEM) as a Cloud Service
  • Edge Delivery Services (EDS)

Issue/Symptoms

  • Published assets (e.g., PDFs, images, or videos) return an HTTP 404 when accessed via EDS URLs.
  • Browser network logs or error messages include: x-error [ static: content] S3: Not Found.

Resolution resolution

To resolve the issue, follow these steps:

  1. Ensure the Asset is published. Add /content/dam (or /content) to the includes array in the config.json file. Note: AEM Assets (such as PDFs, images, and videos) are stored under the /content/dam path in AEM. If the EDS configuration (config.json) does not include /content/dam in its includes array, the EDS backend will not recognize or deliver any content from that path.

    code language-none 
    "includes": [               "/content/"        ]

  2. Assign the appropriate Edge Delivery Services Cloud Configuration to the DAM folder containing the asset. For steps, refer to Assigning a Proper Configuration to an Asset Folder in the Adobe Experience Manager.

  3. Republish the Asset and the Referencing Pages.

  4. After updating configuration and republishing, verify that authored pages and templates reference assets are stored in the correct DAM folder. Ensure those assets are included in the EDS configuration. Preview the page and test referenced asset URLs directly in .aem.live to ensure proper delivery.

Configure your content source in one click for Edge Delivery Services in the AEM as a Cloud Service User Guide.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f