Introduction to Edge Delivery Services in Cloud Manager edge-delivery-services
Edge Delivery Services is a composable set of services that allows for a high degree of flexibility in how you author content on your website. This ability lets you do the following:
- Create fast sites with a perfect Lighthouse Score.
- Continuously monitor performance through Operational Telemetry.
- Increase authoring efficiency by decoupling content sources.
You can use both AEM content management and WYSIWYG authoring using the Universal Editor and document-based authoring.
Cloud Manager in AEM as a Cloud Service lets you enable the Edge Delivery Service for your project.
About Edge Delivery Services in Cloud Manager edge-in-cloud-manager
If you have licensed Edge Delivery Services as part of Adobe Experience Manager Sites, you can onboard your site with Edge Delivery Services directly in Cloud Manager and go live using a guided, self-service experience.
Additionally, you can access a unified experience for managing all your AEM properties while ensuring consistency across key workflows. These workflows include domain name management, SSL certificate management, and CDN mappings.
Cloud Manager offers two deployment types for Edge Delivery Services in Adobe Managed CDN with distinct capabilities. Learn more.
Edge Delivery Services deployment options in Adobe Managed CDN edge-delivery-deployment-options
There are two deployment types for Edge Delivery Services in Adobe Managed CDN:
-
With an existing AEMaaCS environment — Set up an HTTP proxy from an existing AEM Sites as a Cloud Service environment. This approach is typically used when you already have an existing environment and you want to migrate part of a site to Edge Delivery Services. See Setup a proxy from an existing environment.
-
Without an existing AEMaaCS environment (Edge Environment) — Set up a new Edge Delivery site independently of an AEM Sites as a Cloud Service environment. This approach is used when you do not have an AEM Author or publish environment and you want to use Edge Delivery Services on its own. See Setup an Edge Delivery site without an existing environment.
These two options also have different capabilities:
- Config Pipeline is available for AEM as a Cloud Service environments.
- Config Pipeline is currently available for Edge environments only by way of the limited Beta program.
For full setup instructions, see Adobe Managed CDN
About Edge Delivery Services with AEM authoring (Beta) eds-aem-authoring
Modern web experiences require high-performance delivery, but many organizations also rely on established AEM authoring workflows, governance, and content reuse patterns. To help your teams modernize delivery without disrupting authoring, Cloud Manager introduces capabilities that let you do the following:
- Deliver experiences using Edge Delivery Services.
- Continue using AEM Author for content creation.
- Provision only the infrastructure required for your architecture.
These capabilities let organizations adopt modern delivery incrementally, without sacrificing existing workflows.
Authoring options for Edge Delivery sites authoring-options-eds
When you create an Edge Delivery site in Cloud Manager, you can choose your preferred authoring approach:
- Document-based authoring — Author content in Google Drive or SharePoint. No AEM environment is required.
- AEM authoring — Author content in AEM using the Universal Editor. This method requires an AEM Author environment. With this option, a publish tier is not required when Edge Delivery handles content delivery.
Organizations can choose between these approaches, or use both incrementally, depending on their workflow preferences. See Create your first Edge Delivery site with one click.
Flexible publish tier flexible-publish-tier
Cloud Manager lets you configure whether a publish tier is provisioned for your program’s environments. Not all architectures require a publish tier as seen in the following table:
By enabling the publish tier only when needed, teams can provision environments faster, simplify infrastructure, and reduce unnecessary components. See Flexible Publish Tier (Beta).
Benefits of using the Adobe recommended path for Edge Delivery Services recommended-path-eds
Maximize your benefits from Adobe by accessing and consuming your Edge Delivery Services license through Cloud Manager. Doing so lets you take advantage of several key benefits.
- Consume your license on your chosen program, or update other programs, or both.
- Use an external Git repository (Bring Your Own Git) to sync and deploy your Edge Delivery Services site code. To leverage this capability, you must first onboard your site in Cloud Manager.
- Use the Edge Delivery Config Pipeline to configure Adobe-managed CDN settings for your Edge Delivery site by defining rules such as traffic filters, origin selectors, and redirects.
- Take advantage of API-first benefits for performing CRUD (Create, Read, Update, Delete) operations.
- Access SLA reporting.
- Gain access to Adobe support for your registered production programs.
If you have an Edge Delivery Services (EDS) license, you can use an Adobe-managed CDN for your Edge Delivery site. Doing so enables self-service CDN management and DV certificates that renew automatically every three months unless you delete the certificate.
Alternatively, if you choose to use your CDN (that is, a non-Adobe-managed CDN), regardless of your Edge Delivery Services licensing, you must configure it on the aem.live platform. See BYO CDN Setup.
About adding Edge Delivery Services to a production program or sandbox program about-adding-eds-to-prod-sandbox
An Edge Delivery Services can be added in a number of different ways depending on how you began your project or when you want to create the site.
In the wizard, under the Solutions & Add-ons tab, select Edge Delivery Services.
In the Edit Program dialog box, under the Solutions & Add-ons tab, select Edge Delivery Services.
When you create a sandbox program, Edge Delivery Services is added to the program by default; you do not need to select it.
Existing sandbox programs prior to the general availability of Edge Delivery, inherit Edge Delivery Services automatically.
- To add or edit programs, you must be a member of the Business Owner role or be given permission to do so.
- Your organization must have an unused Edge Delivery Services license before it can be applied to a Production program.
- Once the Edge Delivery Services license is applied to or removed from a program, the change takes effect immediately without the need to run a pipeline.
About the Edge Delivery to-do list in Cloud Manager ed-todo-list
The Edge Delivery to-do list in Cloud Manager is an onboarding task checklist meant to guide you through onboarding, managing your Edge Delivery site all the way to Go-Live.
Create a site now
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 (
.hlxURL).
- URL of the live website. For example: