<h3 data-start="634" data-end="656"><strong data-start="638" data-end="654">Introduction</strong></h3>
<p data-start="657" data-end="1213">Blue-Green Deployment is a deployment strategy that minimizes downtime and deployment risk by maintaining two identical environments—one live (blue) and one idle (green). Adobe Cloud Manager for Adobe Experience Manager (AEM) integrates Blue-Green Deployment to enhance application availability, ensuring seamless production updates without service disruptions. This model is available for Adobe Managed Services (AMS) customers using Cloud Manager and enables them to self-manage AEM environments in the cloud while reducing deployment downtime.</p>
<h2 data-start="634" data-end="656"><img loading="lazy" decoding="async" class="alignnone size-medium wp-image-12902" src="https://apiblog.cloudastra.co/wp-content/uploads/2025/02/Blue-Green-Deployment-Model-in-Adobe-Cloud-Manager-for-AEM-300x300.png" alt="" width="300" height="300" srcset="https://apiblog.cloudastra.co/wp-content/uploads/2025/02/Blue-Green-Deployment-Model-in-Adobe-Cloud-Manager-for-AEM-300x300.png 300w, https://apiblog.cloudastra.co/wp-content/uploads/2025/02/Blue-Green-Deployment-Model-in-Adobe-Cloud-Manager-for-AEM-150x150.png 150w, https://apiblog.cloudastra.co/wp-content/uploads/2025/02/Blue-Green-Deployment-Model-in-Adobe-Cloud-Manager-for-AEM-768x768.png 768w, https://apiblog.cloudastra.co/wp-content/uploads/2025/02/Blue-Green-Deployment-Model-in-Adobe-Cloud-Manager-for-AEM-96x96.png 96w, https://apiblog.cloudastra.co/wp-content/uploads/2025/02/Blue-Green-Deployment-Model-in-Adobe-Cloud-Manager-for-AEM.png 1024w" sizes="auto, (max-width: 300px) 100vw, 300px" /></h2>
<h3><strong>1. What is the Blue-Green Deployment Model?</strong></h3>
<p data-start="1269" data-end="1443">A Blue-Green Deployment creates a replica of the existing publish/dispatcher tiers in a Cloud Manager CI/CD pipeline. This model establishes two identical environments:</p>
<p><strong data-start="1447" data-end="1468">&#8211; Blue Environment:</strong> Hosts the current live application version.</p>
<p><strong data-start="1517" data-end="1539">&#8211; Green Environment:</strong> Hosts the new application version and remains idle until tested and approved.</p>
<p data-start="1621" data-end="1744">Once the green environment is verified, production traffic is directed there, and the blue environment is decommissioned.</p>
<h3><strong>2. How Does the Blue-Green Model Work?</strong></h3>
<p data-start="1795" data-end="1932">The Blue-Green Deployment strategy improves availability by reducing downtime and mitigating deployment risks. Here’s how it works:</p>
<p>1. A replica (green environment) is created for testing.</p>
<p>2. Once testing is complete, the production load balancer is switched to the green environment.</p>
<p>3. The blue environment is decommissioned, and new instances are generated for the next cycle.</p>
<p data-start="2189" data-end="2309">In this model, all existing dispatcher and publisher servers are terminated post-deployment, and new ones are created.</p>
<div><img decoding="async" style="width: 80%; height: auto;" src="https://www.tothenew.com/blog/wp-ttn-blog/uploads/2023/03/Cloud-Manager-AMS.png" alt="Blue-Green Deployment Model" /></div>
<h3><strong>3. What is in Scope?</strong></h3>
<p>Only the production publish and dispatcher instances.</p>
<h3><strong>4. What is Not in Scope?</strong></h3>
<p>Author Instance.</p>
<h3 data-start="2475" data-end="2505"><strong data-start="2479" data-end="2503">5. What is the Cost?</strong></h3>
<p data-start="2506" data-end="2647">There are no fees for customers who use Blue/Green deployments. It is a benefit of being an AMS customer and using Cloud Manager.</p>
<h3><strong>6. Who is Eligible?</strong></h3>
<p>All AMS customers who have completed horizontal scaling (Autoscaling) readiness and are using Cloud Manager for production deployments are eligible.</p>
<h3 data-start="2815" data-end="2867"><strong data-start="2819" data-end="2865">7. How Long Can We Keep the Green Servers?</strong></h3>
<p data-start="2868" data-end="3045">The green servers remain available for 24 hours after creation. If not added to the production load balancer within this period, the pipeline fails, and a rollback occurs.</p>
<h3><strong>8. Deployment Duration</strong></h3>
<p>Stage deployment – 30 mins<br />
Production deployment – 3 to 4 hours</p>
<h3><strong>9. Here Are the Detailed Steps for a Blue/Green Deployment</strong></h3>
<p>Production deployment deploys the changes to Stage instances again, followed by approval to Production instances. The following deployment steps will be applicable when the mentioned configurations are updated in the pipeline:</p>
<p>Deployment Trigger is “Manual” in Stage<br />
Deployment Option is “Approve After Stage” in Stage<br />
Deployment Option is “Use Go-Live Approval” in Production<br />
Other deployment options, such as “scheduled” or “use CSE Oversight,” are available.</p>
<div><img decoding="async" style="width: 80%; height: auto;" src="https://www.tothenew.com/blog/wp-ttn-blog/uploads/2023/03/Screenshot-2023-03-16-112408.png" alt="Deployment Steps" /></div>
<h3><strong>10. How to Validate Changes Using a Load Balancer Following a Blue-Green Deployment Model</strong></h3>
<p>1. Modify your local hosts file at that time to point the domain to the Application Gateway IP address.</p>
<p>2. The load balancers’ IPs are listed below. These IPs will not change and will remain constant.</p>
<p>Blue (Live) Application Gateway Static Public IP –xx.xxx.xxx.xx<br />
Green (New) Application Gateway Static Public IP –yy.yyy.yyy.yyy</p>
<p>Example entry in hosts file – yy.yyy.yyy.yyy www.domain.com</p>
<p>3. Following the above host entry, when you access www.domain.com in your browser, you will be directed to the green load balancer where the new code is deployed.</p>
<p>4. You can remove the entry from the host file once you have tested your changes in the load balancer. After that, when you visit www.domain.com, you will be directed to the CDN.</p>
<p>5. After a successful production Blue/Green deployment, the IPs of the production publish, and the dispatcher will change. You must obtain the new IPs from the Adobe Runbook or contact Adobe CSE.</p>
<h3><strong>11. How to Rollback</strong></h3>
<p><strong>Option</strong> 1: Rollback the necessary changes in the Git repository, push them to the Cloud Manager Git repository, and rerun the pipeline for production deployment (Recommended)<br />
<strong data-start="4680" data-end="4693">Option 2:</strong> Restore from a data volume backup (handled by Adobe CSE).</p>
<h3><strong>12. Pros and Cons of Using the Blue-Green Model in Cloud Manager</strong></h3>
<h4><strong>Pro’s</strong></h4>
<p>1. It is simple to clear the dispatcher cache via the pipeline after deployment.<br />
2. Dispatcher syntax can be validated during the security check stage.<br />
3. It’s easy to use, and updating the release branch details in the pipeline is simple.<br />
4. There is no downtime for author/live websites during deployment.<br />
5. Handle the Production deployment without the assistance of Adobe CSE unless there are any pipeline issues.<br />
6. Before making the code/configuration changes live, the Green instance can be thoroughly tested.</p>
<h4><strong>Con’s</strong></h4>
<p>1. Security and performance checks are not available in non-production pipelines.<br />
2. Since there’s no separate pipeline for dispatcher changes, we may have to wait more than 2 hours to implement the changes, even though single-line dispatcher configuration changes take the same time.<br />
3. The Blue-Green deployment model is time-consuming because it takes 3 to 4 hours to complete the Production deployment.<br />
4. Data inconsistency is a significant concern when content authors replicate any pages/assets during deployment, and those published contents/assets are not in sync with the Green instance. If customers report the problem, we may need to republish those pages/assets.<br />
5. We will be unable to examine if any deployment stage in Cloud Manager fails since there are no cloud manager logs available in the deployment console, and we will need to contact Adobe CSE to share the logs.<br />
6. Rollbacking to a previous code version/dispatcher changes via Cloud Manager may take 2 to 3 hours.<br />
7. Publisher/Dispatcher IP addresses do not remain consistent after each Production deployment.<br />
8. If any stage fails, we must restart the Production pipeline from the beginning.</p>
<h3 data-start="5687" data-end="5707"> </h3>
<h3 data-start="5687" data-end="5707"><strong data-start="5691" data-end="5705">Conclusion</strong></h3>
<p data-start="5708" data-end="5988">Blue-Green Deployment in Cloud Manager optimizes AEM application deployments by minimizing downtime and improving reliability. This model enables organizations to efficiently test and validate changes before making them live, ensuring a seamless transition between versions.</p>
<p data-start="5990" data-end="6313"><a href="https://cloudastra.co/blogs/exploring-blue-green-deployment-and-devops-practices-for-open-source-projects">By leveraging Blue-Green Deployment and following DevOps practices</a>, businesses can enhance deployment workflows and maintain high application availability. If your organization relies on Cloud Manager for AEM deployments, adopting this strategy can streamline operations and improve overall deployment efficiency.</p>
<p>Do you like to read more educational content? Read our blogs at<a href="https://www.cloudastra.co/blogs"> Cloudastra Technologies</a> or contact us for business enquiry at <a href="https://www.cloudastra.co/contact">Cloudastra Contact Us</a></p>


Blue-Green Deployment model in Adobe Cloud Manager.

Blog Details

Blue Green Deployment: Understanding the Basics

Blue Green Deployment: Understanding the Basics

Share This Article

Follow Us