Metabase Elastic Beanstalk - RDS Postgres Setting location on EC2


I went thru this document and setup Metabase

I was trying to import our metabase backup from another server into this new server, and I did not see any metabase table on the RDS postgres server.

Does any one have any insight?


Hi @Toga
Make sure you have backups.
Post “Diagnostic Info” from Admin > Troubleshooting from the old server. It sounds like it’s not even using RDS for the application database, which means it’s stored in H2 on the instance, which means it will be lost if you restart that instance.
You should keep the RDS separate/decoupled from the EBS - you might want to read these too:
Best practice for having RDS as part of EB environment
Elastic beanstalk app rebuild fail -> RDS restore 'backend' seems to work but can't acces http interface. any aws pro's want to freelance support?

Hi Flamber,

Our old metabase is non-aws, I am moving the non-aws backup into rds, but I am unable to find where the existing data is store, i figured it would be stored in RDS.

I will see if i can find it in the metabase server

@Toga I don’t understand. So you have manually dumped from local Postgres and loaded it into an RDS, but the data isn’t there?

I dump from a non-aws mysql sql server, but I have not imported it into the rds, as i am unable to find the new metabase tables.

@Toga Metabase doesn’t support EBS on MySQL RDS: - upvote by clicking :+1: on the first post

the rds is postgres, I am asking where I should be able to locate the metabase database, on the rds postgres, or the ec2 local?

@Toga You cannot copy a MySQL schema to a Postgres schema without doing conversion.
It sounds like your question has nothing to do with Metabase, but is a general AWS question:

ok thank you, but where is the actual metabase table located? in rds or on the local ec2?

@Toga I don’t understand what you’re asking. If you have followed the EBS guide, then the application database is setup on RDS.

Yes I have followed the setup guide:

However, when i am connected to the postgres rds, I see 3 databases:

@Toga Post “Diagnostic Info” from Admin > Troubleshooting.


“browser-info”: {
“language”: “en-US”,
“platform”: “MacIntel”,
“userAgent”: “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36”,
“vendor”: “Google Inc.”
“system-info”: {
“file.encoding”: “UTF-8”,
“”: “OpenJDK Runtime Environment”,
“java.runtime.version”: “11.0.8+10”,
“java.vendor”: “AdoptOpenJDK”,
“java.vendor.url”: “”,
“java.version”: “11.0.8”,
“”: “OpenJDK 64-Bit Server VM”,
“java.vm.version”: “11.0.8+10”,
“”: “Linux”,
“os.version”: “4.14.192-147.314.amzn2.x86_64”,
“user.language”: “en”,
“user.timezone”: “GMT”
“metabase-info”: {
“databases”: [
“hosting-env”: “elastic-beanstalk”,
“application-database”: “postgres”,
“application-database-details”: {
“database”: {
“name”: “PostgreSQL”,
“version”: “12.3”
“jdbc-driver”: {
“name”: “PostgreSQL JDBC Driver”,
“version”: “42.2.8”
“run-mode”: “prod”,
“version”: {
“date”: “2020-08-17”,
“tag”: “v0.36.4”,
“branch”: “release-0.36.x”,
“hash”: “196c1f6”
“settings”: {
“report-timezone”: null

@Toga I don’t know. You must have multiple RDS running. Metabase will connect and create tables in the database.

i am not that great with docker, so this is a learning experience… i just found another article that pointed me towards docker inspect

        "Env": [

so the db_name shows was configured as ebdb… i would like to find where the actual metabase settings are being stored. i think they are being stored in a local. i checked 4 of the elastic beanstalks i setup, and they all have the ebdb.

@Toga The Metabase data is stored in the configured application database - which is ebdb on RDS in your case.

so if i terminate the ec2, you are saying everything has been stored in ebdb…so it will be all repopulated

@Toga Yes, if the RDS is decoupled from the EBS, like I said in my first comment - Metabase Elastic Beanstalk - RDS Postgres Setting location on EC2

I finally found it, it was store under ebdb under a public schema, which was not being displayed.


1 Like