@flamber, That’s what stumped me last time, if indeed the JSON is the where a selection of DB can be affected, it isn’t in the zip explicitly, only a handful of small files. Having looked thru their contents it’s not obvious to me what they’re all doing, is an image being pulled from somewhere, Docker, Github?
From the Configuring RDS for Metabase, “… Metabase also supports MySQL/Maria DB as backing databases…” it should be possible. But it’s not a simple matter of customizing the beanstalk environment such as with a dropdown, for example, as implied here in #9021. Choice of backing DB apparently takes the manipulation of code somewhere, but where, how, and does it take learning how to use Docker, Github, or some combination to do that?
There is also an after the fact migration option from Configuring RDS for Metabase that may or may not be possible or at least rather complicated in a beanstalk environment.
Attaching to an existing DB as discussed in Best practice for having RDS as part of EB environment may offer another avenue. Adding to the 01_metabase.config file is intriguing but Amazon’s decoupling method is just plain nuts!
Why does it have to be this hard to do a simple database selection? At some point this would be an excellent candidate for a one click, one dropdown type of solution, something accessible to everyone.
In the meantime, just point me in the right direction, how can MySQL be the backing database for a Metabase beanstalk environment?