Deploying a highly available database solution in the Amazon EC2 Cloud using MariaDB

Replication and High Availability Strategies
23 April 3:50pm - 4:40pm @ Ballroom D

How can you create a template for deploying a Highly Available database in the Amazon EC2 Cloud? How can you get redundancy and automated failover, all based on standard Open Source components?

The solution describes how to use Pacemaker and Corosync for control, and how to use Elastic IP address, Elastic Block Storage and EC2 Linux instances in Amazon.

With the template, you can automate the deployment of a database cluster. The solution includes startup synchronisation, automated Pacemaker configuration, MariaDB Master promotion, Elastic IP migration and node maintenance.

The goal of the template is also to produce a system that will allow repeatable and highly automated deployments of a database cluster within the Amazon EC2 Cloud environment.

We look at how to use the security features of Amazon's IAM subsystem to allow automated control using the Pacemaker and Corosync Linux HA tools.


Massimiliano Pinto
Senior Software Engineer, MariaDB Corporation
Massimiliano has worked for almost 15 years in Web Companies playing the roles of Technical Leader and Software Engineer. Prior to joining SkySQL/MariaDB he worked at Banzai Group and Matrix S.p.A, big players in the Italy Web Industry. He is still a guy who likes too much the terminal window on his Mac. Apache modules and PHP extensions skills are included as well.
Mark Riddoch
Staff Engineer, Dianomic Systems
Mark has worked in the computer industry for almost 30 years, this has included many roles in various software companies developing network and imaging applications. Mark is currently working at Diatomic Systems as an architect and senior engineer on industrial IoT products we an empathises on data management for IoT. Prior to that he was a staff engineer at VMware working on the database implementation within vCloud Air, he also worked for SkySQL, now known as MariaDB Corporation, in the engineering department. Here he designed and implemented database tools and the MaxScale database proxy. Previously he was at Sybase as chief designer and project leader for the ASE kernel development team, where he re-architected the ASE kernel.