I need to sync two websites. One is online and another is local. How can I fetch database data from Amazon server to localhost(xammp)?
MySQL server on your localhost can connect to Amazon mysql database if you have open port 3306 on Amazon server. You can setup replication between Amazon server and localhost for live sync.
Otherwise you can setup a script which copies the binary logs from Amazon server and applies them on localhost.
Related
Goal
I am trying to use MongoDB's BI Connector for Tableau, aka mongosqld. I have version 2.10, so here are the docs.
My long-term goal is to host mongosqld as a service on an AWS EC2 instance, and host MongoDB on AWS DocumentDB.
Background
A successful set of baby steps was:
Host MongoDB in a Docker container on my local machine via mongo image
Manually run mongosqld on my local machine, without a schema
Connect to it via mysql from my local machine
This works fine, I could see all of the databases via show databases;
My next set of steps was:
Host MongoDB in AWS DocumentDB
Host mongosqld on my EC2 instance at address 0.0.0.0:3307, without a schema
Enable TCP comms on port 3307 and 27017
Connect to it via mysql from my local machine
When I use mysql shell's show databases; command, I cannot see my databases, only information_schema and mysql.
Question
Given all of this information, does anyone here know what might have gone wrong? I am currently at a loss for what to try next.
What tool can I use to run sql profile against a AWS Aurora or AWS Mysql database? Seems like a simple task that I have done many times against local mysql sql db or ms sql server, but for the life of me I cannot get to work. Is this something that can be done? I have been trying to use Neor Profile without success. However, I'm able to use Neor Profile successfully on my local mysql db.
Because Neor Profile basically serves as a proxy, you have to use port 4040 in your application and then Neor connects to AWS via port 3306. I can successfully get Neor Profile 'profiling' against the AWS db but when I run my local application or mysql workbench, via port 4040, it doesn't connect, with a general connection error.
My question, which I can't find by searching the Internet or help files is...Can you perform a sql profile against a AWS Aurora or AWS Mysql database?
I have a Talend Data Integration server (subscribtion product) and I want to load date to/from a MySQL database which is reachable over VPN tunnel.
Both servers are linux servers (RHEL).
Could you please suggest how can I connect from Talend to MySQL over VPN?
Thanks!
Create an SSH tunnel which makes MySQL appear on your localhost:3306 address then connect to that.
Is it possible to use AWS' RDS MySQL solution in tandem with my current file server host? By that, I mean, can I connect to the RDS MySQL server as I am with my hosts current database?
I've tried the AWS documentation but it seems a bit flaky in this area.
Thank you,
Amazon RDS is a database server, just like any other. If you start up an RDS MySQL server, you can connect to it from anything else that can connect to a MySQL server.
The difference is that you do not have direct host access to the RDS server. Meaning, you cannot SSH into it and get a command prompt.
But you can connect to it from any MySQL client, including MySQL Workbench.
Heroku supports no database other than PostgreSQL, but my question is here regarding remote database. Can a Heroku instance running Rails connect to a remote database connection? To be more specific, the remote database connection of MySQL resides at Amazon RDS.
If it's not possible at all, can I use remote database through HTTP requests generated by Rails code?
Can a Heroku instance running Rails connect to a remote database
connection?
Yes
To be more specific, the remote database connection of MySQL resides
at Amazon RDS.
Yes. See:
https://devcenter.heroku.com/articles/ruby-database-provisioning
https://devcenter.heroku.com/articles/amazon-rds#configuring-a-heroku-ruby-app-to-use-a-mysql-rds-instance
You must grant Heroku dynos access to your RDS instance. The recommended way to do this is to configure the RDS instance to only accept SSL-encrypted connections from authorized users and configure the security group for your instance to permit ingress from all IPs, eg 0.0.0.0/0.