We migrated the Rekindle Postgres db from Heroku to AWS RDS in May 2023. The 2 main reasons for that decision were to introduce a production fallback instance for the case that the main application instance fails & to make the future integration of other AWS services easier. Due to db costs we have remove the fallback instance for the time being, but the read replica can be used for a fallback.
We have a main production database to handle the day-to-day application load with the db identifier: rekindle-production.
Then we have production read replica that mainly handles queries related to data analytics, e.g. to generate report for clients. The db identifier is: rekindle-production-read-replica. The data in the main db is instantly copied into this read-replica database.
Have a staging database that we use for development purposes, it has the db identifier: rekindle-staging.
The credentials for these RDS instances can be accessed via the Secrets Manager in the AWS Rekindle organization. Please handle these credentials securely and responsibly.