Documentation AEM as a Cloud Service User Guide

Manage Edge Delivery site in Cloud Manager manage-edge-delivery-sites

Last update: Tue Mar 31 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

Applies to:
Experience Manager as a Cloud Service

CREATED FOR:

Admin
Developer

Learn how to manage Edge Delivery sites in Cloud Manager by adding a CDN configuration to an existing site. Or, delete an Edge Delivery site.

Add a Domain Mapping to an existing Edge Delivery site add-cdn-to-edge-delivery-site

See Add a Domain Mapping.

Rename an Edge Delivery Site (#rename-edge-delivery-site)

In Adobe Cloud Manager, you may want to rename an Edge Delivery site for several reasons:

Clarity and organization: To describe the site’s purpose better or its associated environment (for example, production, staging).
Avoiding confusion: If multiple sites are in use, renaming can help easily differentiate between them, reducing the chance of applying configurations or updates to the wrong site.
Standardization: To follow a consistent naming convention that aligns with your organization’s guidelines for easier management and auditing.

To rename an Edge Delivery site:

Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate program.
On the My Programs console, select the program with Edge Delivery Services configured, where you want to add an Edge Delivery site.
Do either one of the following:
- From the Program Overview page, click the Edge Delivery tab. In the Edge Delivery site table, click the ellipsis at the end of a row whose site you want to rename.
  Click Rename.
- In the upper-left corner of the page, click to reveal the left side menu. Under the Services heading, click Edge Delivery Sites.
  In the Edge Delivery site table, click at the end of a row whose site you want to rename. Click Rename.
In the Edit Edge Delivery Site dialog box, in the Site Name text field, enter the new name of the site.
Click Edit.

Activate the publish tier for an Edge Delivery site (Beta) activate-publish-tier-for-eds

NOTE

The publishing feature described here is in Beta. To join the Beta, email grp-beta_xwalk-publish_config@adobe.com with your Adobe Organization ID and Program ID.

This capability applies only to Edge Delivery sites created with the AEM Authoring option in Programs where the flexible publish tier feature is enabled.

If your Edge Delivery site uses AEM authoring, the publish tier is not provisioned by default because Edge Delivery handles content delivery. However, you can activate the publish tier at any time if your site requires it. For example, if you need to support traditional AEM publishing alongside Edge Delivery.

After your Edge Delivery site is created and its status shows Verified in Cloud Manager, you can author and publish content using the AEM Universal Editor.

To access the Universal Editor from Cloud Manager:

On the Edge Delivery tab, in the Edge Delivery sites list, locate your site.
Click the Content Source link in the site’s row. The link opens the AEM Universal Editor page, from which you can create and edit content for your site.–>

To activate the publish tier for an Edge Delivery Site:

On the Program Overview page, under the Publish Delivery tab, in the Environment card, click the Information icon.
In the informational pop-up, under Publish URL, select Click to activate to enable publish tier provisioning in the Cloud Manager user interface.
In the Activate Publish tier dialog box, click Activate.

Once activated, the publish tier is provisioned automatically. Alternatively, the publish tier can be provisioned automatically if the author tries to publish content from the AEM user interface directly.

After the publish tier is activated and provisioned successfully, the Click to Activate link becomes dimmed/unavailable.

From AEM Author — In the AEM authoring interface, click Quick Publish to publish content directly to your Edge Delivery site. The publish tier is not required for this operation when Edge Delivery handles delivery.

After publishing, preview your content at your site’s .page URL, or view it live at the .live URL.–>

NOTE

Activating the publish tier adds publish infrastructure to your environment. This functionality may affect your program’s resource consumption. To configure whether the publish tier is required at the program level, see Flexible Publish Tier (Beta).

Delete an Edge Delivery site delete-edge-delivery-site

If you delete an Edge Delivery Services site, any associated CDN configurations are removed as well. This action breaks the connection between custom domains and the site. For more details, see CDN configurations.

To delete an Edge Delivery site:

Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate program.
On the My Programs console, select the program with Edge Delivery Services configured, where you want to add an Edge Delivery site.
Do either one of the following:
- From the Program Overview page, click the Edge Delivery tab. In the Edge Delivery site table, click at the end of a row whose site you want to remove.
  Click Delete, then click Delete again to confirm the site’s removal.
- In the upper-left corner of the page, click to reveal the left side menu. Under the Services heading, click Edge Delivery Sites.
  In the Edge Delivery site table, click at the end of a row whose site you want to remove. Click Delete, then click Delete again to confirm the site’s removal.

Manage an Edge Delivery site between Helix 4 and Helix 5

Use the /program/{programId}/site/{siteId} API endpoint to migrate an Edge Delivery site between Helix 4 and Helix 5.

IMPORTANT

CDN configurations for Helix 4 websites cannot be migrated to Helix 5 automatically. This limitation exists because customer production sites may still run on Helix 4, while their Helix 5 versions are still in development.

Prerequisites

The sitename must already exist.
Know the appropriate branchName, Helix version, and repo values.
Migration only modifies branchName, Helix version, and repo. The owner field cannot be changed.

API format

PUT /api/program/{programId}/site/{siteId}

Request body parameters
Creates an override for an Edge Delivery site to enforce the origin specified in the request body.

{
  "sitename": "<required site name>",
  "branchName": "<git branch>",
  "version": "v4" | "v5",
  "repo": "<git repository name>"
}

Example 1: Migrate to Helix 5

http

PUT /api/program/{programId}/site/{siteId}

json

{
  "sitename": "test-site-new-helix5",
  "branchName": "branch",
  "version": "v5",
  "repo": "my-website"
}

Origin URL result
Returns an Edge Delivery site with the following origin URL:

"origin": "branch--my-website–Teo48.aem.live"

Example 2: Migrate to Helix 4

http

PUT /api/program/{programId}/site/{siteId}

json

{
  "sitename": "test-site-new-helix4",
  "branchName": "branch",
  "version": "v4",
  "repo": "my-website"
}

Origin URL result
Returns an Edge Delivery Site with the following origin URL:

"origin": "branch--my-website--Teo48.hlx.live"

Example 3: Migrate repoless site to Helix 5

http

PUT /api/program/{programId}/site/{siteId}

json

{
  "sitename": "test-reposless-website",
  "branchName": "main",
  "version": "v5",
  "repo": "my-reposless-website"
}

Origin URL result
Returns an Edge Delivery site with the following origin URL:

"origin": "main--my-repoless-website--Teo48.aem.live"

Log a support ticket eds-support-ticket

If a product issue needs additional investigation and troubleshooting and must meet response SLTs, you can submit a support ticket.

To log a support ticket, you must first register your Edge Delivery site in Cloud Manager. Registering your website with Cloud Manager is recommended to all AEM as a Cloud Service users and brings a number of benefits. See the Cloud Manager documentation for details if you have not already registered your site.

To log a support ticket:

Follow the standard support process and create a ticket.
Add Edge Delivery in the title of the ticket.
In the description, provide the following details in addition to the problem description:
- URL of the live website. For example: www.mydomain.com.
- URL of the origin website (.hlx URL).

recommendation-more-help

fbcff2a9-b6fe-4574-b04a-21e75df764ab