Currently using AWS RDS is not an officially supported configuration and would fall in the scope of CRS. This feature request is to make this an official supported configuration as well as create documentation on how to configure it.

This type of configuration is common and desirable as it provides a level of HA that the product does not currently provide on it's own.

Support case description from engineer attempting to configure AWS RDS with 3scale:

What problem/issue/behavior are you having trouble with? What do you expect to see?

During installation with an external database. we saw that the db tables were being created, but the tables were not being properly populated.

There was very little information/ or direction we could glean to be able to self diagnose this condition.

Upon manually attempting to run the db:seed

rsh into the system-app pod
rsh$ bash
bash$ bundle exec rake db:seed

we were able to see the resulting error

Caused by:
Mysql2::Error: You do not have the SUPER privilege and binary logging is enabled (you might want to use the less safe log_bin_trust_function_creators variable)

We then applied this to RDS and made sure to modify and to apply/restart the db.

This then allowed the DB to be seeded and API to come up. This was very difficult/time consuming to debug, and there did not appear to be any sufficient official documentation specifically around the necessary mySql configuration required for 3Scale to successfully install and populate the DB.

Where are you experiencing the behavior? What environment?

AWS with External MySQL Research lab environments

When does the behavior occur? Frequently? Repeatedly? At certain times?

Repeatedly if the DB is not setup correctly

What information can you provide around timeframes and the business impact?

Would be a difficult debugging situation in a client environment where access/control/administration of the external/shared MySQL database is not available to the consultants or installer of 3Scale