Using RDS with juju

Is there a comprehensible guide to use RDS with juju charms (databases in aws) very much like this post describes?

… or is this a charm specific thing to implement…

Not yet. I have something nearly ready for public testing. Probably this week.

Conceptually, it’s quite a simple problem to solve. However, I have tried to create a gold-plated charm that is very feature-rich. I’ll reduce my ambition and get something that people can play with.

1 Like

We’ve been looking at doing proxy charms/infrastructure charms for a while, this might be a great candidate for one.

One of the big setbacks atm in non-k8s charms is the requirement of a machine to run the charm code, which is pretty wasteful. These could be done as subordinate charms, but still seems heavy handed.

Need to think more about this use case.

Hi @erik-lonroth, here is my prototype. If you provide it with the right config values, it works just like the standard postgresql charm.

1 Like

Link doesn’t work for me…

Would it be possible to use this guide as a basis to try this out in AWS for a test of using with a nextcloud deploy?

It can take a few hours for the site to refresh. It’s a little annoying.

It might be useful to create a dedicated RDS charm and use juju trust to pass credentials through to the charm.

On my side, I developped my charms to both support a “custom MySQL servers” or a MySQL relation.

Basically I have a config named “external-mysql” that if you set to true, will use the “external-mysql-hostname/username/port” rather than the relation in the charm that requires MySQL.

1 Like

Still not working. This situation is common for me aswell over some charms I have published previously.