During the past 2+ years we’ve deployed a number of single- and multi-server Zimbra systems on Amazon Web Services (“AWS”). While Zimbra has a number of Deployment Guides, they are generic by nature and do not describe how to leverage AWS features to maximize cost savings, reliability, performance and security. At this writing, Zimbra has no Reference Architectures for AWS hosting, let alone choices for aggressive RPO/RTO targets (at higher costs) vs. more modest RPO/RTO targets.
Further, our experience has been that even seasoned Zimbra system administrators can find the transition to hosting on AWS somewhat challenging, too often resulting in suboptimal architecture choices that increase costs, reduce performance, reliability etc.
Consequently, in 2018 we created a PowerPoint covering Zimbra Hosting on AWS – Best Practices From The Field. Given the fullness of time, the evolution of services at AWS, and the improvements in Zimbra, that presentation now contains too many out-of-date concepts to be as useful as it was two years ago. We have consequently replaced that PowerPoint presentation with a new Architectural Design Reference for Large Zimbra Deployments blog post.
That new blog post describes spreading a multi-server Zimbra system across multiple AWS Availability Zones. But if you have just a single Zimbra server, no problem! You have two choices: You can use the architectural guidelines in the blog post, but just put your single Zimbra server in a single Availability Zone, or; you can increase redundancy and resiliency by adding a second LDAP/MTA/Proxy server in a second Availability Zone.
Hope that helps!
L. Mark Stone
Mission Critical Email
18 November 2020
The information provided in this blog is intended for informational and educational purposes only. The views expressed herein are those of Mr. Stone personally. The contents of this site are not intended as advice for any purpose and are subject to change without notice. Mission Critical Email makes no warranties of any kind regarding the accuracy or completeness of any information on this site, and we make no representations regarding whether such information is up-to-date or applicable to any particular situation. All copyrights are reserved by Mr. Stone. Any portion of the material on this site may be used for personal or educational purposes provided appropriate attribution is given to Mr. Stone and this blog.