DocumentationExperience Cloud KCS

AEM as a Cloud Service: Understanding ‘delivery’ instances and environment mapping

Last update: September 1, 2026

This article describes the appearance of delivery instances in Adobe Experience Manager as a Cloud Service and explains how these instances are mapped when Content Hub is enabled.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service
  • AEM Assets Content Hub

Issue/Symptoms

  • Additional environment instances with names ending in -delivery (such as -stage-delivery, DEV, and PROD) appear in the Adobe Admin Console under AEM as a Cloud Service.
  • Only the standard author and publish instances are expected.
  • The purpose of the delivery instances and their relationship to existing AEM environments is unclear.
  • The mapping between some environments, such as Stage, and their corresponding delivery instances isn’t obvious.

Cause

Delivery instances are automatically provisioned when Content Hub is enabled for an environment in AEM as a Cloud Service. The presence and mapping of these instances depend on which environments have Content Hub enabled and the permissions assigned in the Admin Console.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Understand that when Content Hub is enabled for AEM Assets as a Cloud Service through Cloud Manager, a new instance is automatically provisioned for each environment where Content Hub is enabled. This instance uses delivery as a suffix in its name (for example, -stage-delivery).
  2. Check whether Content Hub is enabled for your Development, Stage, and Production environments. When enabled, the corresponding delivery instances appear in the Admin Console.
  3. Verify the mapping between the Content Hub delivery instance and the AEM environment. Cloud Manager establishes this mapping during the enablement process.
  4. If a delivery instance is missing or isn’t mapped as expected, verify the enablement status for that environment in Cloud Manager. Ensure that Content Hub is enabled for the specific environment.
  5. If you don’t see a delivery instance for a specific environment, verify that your account has the required permissions for that environment in the Admin Console. Product administrators can assign access as needed.
  6. After completing these steps, confirm that the expected delivery instances appear in the Admin Console for each environment where Content Hub is enabled.
recommendation-more-help
experience-cloud-kcs-help-kbarticles