AEM Edge Delivery Service CICD Pipelines from Cloud Manager

[SupportMember]

While re-using the AEM tenant > program, we plan to push out an AEM Edge Delivery Service website, where does the Cloud Manager's CICD pipeline get kicked in? Should AEM Edge Delivery Service be rolled out via Adobe Cloud Manager Pipeline or will just pushing code to private repo to the Repository access settings of the AEM Code Sync App be just enough?

[arunpatidar · Accepted solution]

Hi @SupportMember 

For EDS, its just github repo, no deployment using Adobe Cloud Manager.

However if you want to use Adobe's CDN, then you might need to deploy CDN config using CI/CD but please check this with Adobe

[Saad-A]

Hey Arun,

Wondering why ACM isn't used at all? What's the functionality of the Edge delivery tab in there then? For my client we're trying to setup a DevOps pipeline that gets triggered from .live site (main branch in the github repo) push, which then takes those changes into a production environment (the final .com website of the client, where they can author the content as they wish). 

For more context, we're utilizing Sharepoint for our document authoring as well. Could you provide some guidance on the best way to do this, and how would only github allow this process to be automated? Maybe im missing something. 

Much appreciated. 

[arunpatidar]

HI @Saad-A 

As you mentioned, GitHub is used to deploy the code, and SharePoint is used for authoring content.

However, to handle main domains like https://main--eds--own.hlx.live/ map to https://www.mysite.com/ and other rules, you need to deploy the configuration at the CDN level.

If you're relying solely on Adobe's Fastly CDN, you'll need to use ACM to deploy those changes. Otherwise, you can skip these changes on Adobe's Fastly CDN and configure them on your own CDN instead.