Solved

Support for Blue Green Deployment in AEM Cloud Service ( not in AMS )

Forum|Forum|1 year ago
December 3, 2024
4 replies
1022 views

Please provide support for Blue Green Deployment in Adobe AEM Cloud SErvice, not in Adobe AEM Managed Services. All the documents like this one experts are pointing out is only for AMS. https://www.opsinventor.com/blue-green-deployment-on-adobe-experience-manager/#comment-4832

Please provide guidance or the right documentation. If not available, please provide us a pathway to include this in to an engineering request.

Thanks,

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by arunpatidar

Hi @raeesuzhunnan

In AEMaaCS, deployments use a blue/green strategy for zero downtime. The AEM Author and Publish tiers run as Docker containers managed by a standard Container Orchestration Service. During each deployment, old containers are replaced with new ones by combining a baseline image with deployment packages. The CDN is switched to the new instances, ensuring seamless updates.

All of this happens in the background, so unlike AMS Blue/Green, you cannot pause the process or use both containers simultaneously.

You can raise feature request at https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-ideas/idb-p/adobe-experience-manager-ideas

EstebanBustamante

Community Advisor and Adobe Champion

Hi,

It seems there's some confusion. AEMaaCS cannot be hosted outside of Adobe infrastructure, meaning you must use AMS, so you must adhere to Cloud Manager. One of its main tasks is to deploy code following using the blue/green pattern. Please refer to the details here: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-manager/content/introduction#blue-green

Hope this helps

Esteban Bustamante

Asutosh_Jena_

Community Advisor

Hi @raeesuzhunnan

In AEM as a Cloud Service (AEMaaCS), Cloud Manager handles the deployment process, ensuring that every build is first deployed to the Stage environment before proceeding to Production. This approach guarantees build stability and maintains zero downtime in the Production system, avoiding any disruption for end users.

You can explore the deployment pipeline concepts in detail here:
Deployment Pipelines - Adobe Experience Manager as a Cloud Service

With AEMaaCS and Cloud Manager, deployment to Production is strictly gated by the successful deployment to Stage. If any issues are detected with the build, Cloud Manager prevents it from progressing to Stage, thereby safeguarding the stability of the Production environment.

arunpatidar

Accepted solution

Community Advisor

Hi @raeesuzhunnan

In AEMaaCS, deployments use a blue/green strategy for zero downtime. The AEM Author and Publish tiers run as Docker containers managed by a standard Container Orchestration Service. During each deployment, old containers are replaced with new ones by combining a baseline image with deployment packages. The CDN is switched to the new instances, ensuring seamless updates.

All of this happens in the background, so unlike AMS Blue/Green, you cannot pause the process or use both containers simultaneously.

You can raise feature request at https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-ideas/idb-p/adobe-experience-manager-ideas

Arun Patidar

kautuk_sahni

Community Manager

@raeesuzhunnan Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

Kautuk Sahni

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded