Customer needed an AWS Route53 based custom solution to redirect M2EE maintenance page that masks all clusters of the production environment.
This case study started in February, 2016. It was a period when completely revised Magento 2 version was being launched worldwide!
Magento 2 EE Enterprise Edition with AWS EC2 Architecture with Single AWS EC2 Admin Instance, Four to Sixteen AutoScaling Front-end EC2 Clustered Instances connected via AWS Elastic Load Balancer. Databases used were AWS RDS, AWS Elasticache. Server environment was NGINX with PHP-FPM and Varnish.
Single click facility to place the entire cluster in maintenance mode so that all frontend user of Magento sees a well designed custom maintenance page. This system should be seamlessly integrated into the deployments pipeline. Thus enhance Deployment Automation which is a part of the Build automation echo system.
Since the entire architecture was using AWS Load Balancer with multiple servers connected to it, it was not possible to use Magento 2’s built-in maintenance mode and maintain the atomicity required. The client did not want some customers seeing the live site and some not, which could create inconsistencies in the shopping cart system.
This maintenance mode solution had the additional advantage of acting as a Disaster Recovery system since the flag also was connected to a built-in watchdog system in case of a nasty shop breakdown.
Customer was happy to hide the entire Magento clustered environment under maintenance in a professional and safe manner with Built-in Backup and Rollback rollback mechanism in case of any failures in the DevOps delivery pipeline.