used Synapse to replace RDS

Hi guys,
did you have try synapse to replace RDS?
I have tried it and the result

I, [2017-04-28T09:59:05.870663 #15534] INFO -- Synapse::Synapse: synapse: starting...
I, [2017-04-28T09:59:05.870740 #15534] INFO -- Synapse::ServiceWatcher::Ec2tagWatcher: Connecting to EC2 region: ap-southeast-1
I, [2017-04-28T09:59:06.592645 #15534] INFO -- Synapse::ServiceWatcher::Ec2tagWatcher: synapse: ec2tag watcher looking for instances tagged with Name=staging-synapse
I, [2017-04-28T09:59:06.592795 #15534] INFO -- Synapse::Synapse: synapse: configuring haproxy
W, [2017-04-28T09:59:06.616788 #15534] WARN -- Synapse::ConfigGenerator::Haproxy: synapse: restart required because socket command show stat
failed with error #
I, [2017-04-28T09:59:06.646909 #15534] INFO -- Synapse::ConfigGenerator::Haproxy: synapse: restarted haproxy
W, [2017-04-28T09:59:06.820603 #15534] WARN -- Synapse::ServiceWatcher::Ec2tagWatcher: synapse: no backends for service proddb; using default servers: [{"name"=>"staging-synapse", "host"=>"staging-database.blabla.rds.amazonaws.com", "port"=>5432}]

thanks

The report mentions Synapse's EC2 tag watcher and HAProxy configuration, but names no file, test, or concrete change. First clarify whether the request is support for replacing RDS or help diagnosing the shown fallback to staging-database.blabla.rds.amazonaws.com; only then reproduce the reported startup logs and define what successful behavior should be.

Written by the indexing model from the issue text.