Has anyone used AWD RDS as their backend database?

[Sven]

Hi All,

I'm looking at building an instance in AWS as part of spec for a customer and part of my design is, of course, the database and its availability.

I'm not to clued up on AWS systems but I've spotted their Multi-AZ DB cluster so wondering if there' any up/downsides?

Has anyone used this? Had any issues? How does the backup recovery aspects work, are they as simple as their docs suggest?

Or shall I just roll my own servers with either mysql/maria/postgres and manage it myself?

Thanks!
S.

[roy_li]

Hi Sven

I have used the Multi-AZ DB instance of AWS RDS as zabbix backend database, this solution provides high availability and failover support for DB instances with a single standby DB instance.

This solution is equivalent to the Zabbix standalone deployment solution, only one DB instance provied read/write service for zabbix server.

The difference is that AWS guarantees the availability of this database instance and switches to another standby instance in case of its failure.

This standby instance will always synchronize data from the primary instance, but cannot be accessed



This highly available solution is very stable, with a maximum failover time of no more than two minutes.

As for Multi-AZ DB cluster solution, I don't recommend it for the simple reason that zabbix is not suitable for this kind of scenario that requires read and write classification.

[[email protected]]

The one thing to remember is if you are intending on using TimescaleDB for partitioning/compression, I dont believe the extension is supported at the moment for AWS RDS.
Please correct me if I am wrong as I too was looking at using AWS RDS.