amazon-rds

I have a database instance on RDS with 2 databases on it. Is there a good way using the RDS command line tools to copy the one database to the other? If not, what is the recommended way of doing it? Thanks in advance. I'd use mysqldump to get the tables and then mysql to import them. Update 2014/07/08 : Depending on what you're planning to do here, another solution today is to setup replication and then to promote the slave to be the master. That is for example if you want to update your database's release/version: http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ReadRepl.html If you

I'm new to API Gateway, and as far I have tried is a really powerful tool. For the project I'm working right now we are using a PostgreSQL instance in RDS. I've seen that is possible to access directly to DynamoDB tables from API Gateway, so I was wondering if is there a way to do so for relational databases. So I created a resource with a GET method and configure it to connect to my database, but I wasn't sure if I used the right parameters: Provided information about the target backend So I wasn't sure about the arguments in each setting's field. In AWS Subdomain I wrote the public URL as if

Hi I was having the same problem as this post but the posted answer (no sample code) wasn't provided so I will start a new thread and ask you guys. I have created a AWS Serverless Application (.Net Core) project for our lambda function and below code is what I used to connect in AWS RDS. string ConnectionString = "Data Source=rds4abc1190.asdfqwerqb9l.us-east-1.rds.amazonaws.com,2855;Initial Catalog=MyDatabase;Persist Security Info=True;User ID=myID;Password=mypassword;Encrypt=False"; using (var Conn = new SqlConnection(ConnectionString)) { using (var Cmd = new SqlCommand("SELECT * from

My amazon mysql large RDS instance's CPU utilization is going very high (about 70%) without any genuine reason. How to find which query or process is harming my instance? thanks The standard method is to examine SHOW PROCESSLIST or SHOW ENGINE InnoDB STATUS to see what's going on. You are using InnoDB, right? It could also be due to the autoback feature RDS provides. I think AWS RDS does an automatic back up around midnight everyday, you must factor this into your calculations 来源： https://stackoverflow.com/questions/19053980/rds-instance-cpu-utilization

I am trying to connect to my Amazon RDS (MySQL) instance from a nodejs code hosted in Lambda using the "felixge/node-mysql" package. I need help to find out what I am doing wrong. I am getting "connect ETIMEDOUT" error. My code is hosted in Lambda and both Lamda and RDS are of the same account and region. I have also attached the RDSFullAccess Policy to the IAM role. RDS instance is also accessible from all IPs(no whitelist/blacklisted IPs). At the same time, I am able to connect from my local MySQL Workbench with same credentials. Here is my code: var connection = mysql.createConnection({

I am trying to build a graphQL API with Serverless Framework on AWS-Lambda using Apollo-Server-Lambda etc. I need to use a not publicly available PostgreSQL RDS instance. I can get lambdas up and running and sending back requests when not in VPC. I can get a Postgres RDS Database up and running and connected to PgAdmin (when in publicly available mode). The problem is once I make the RDS Postgres 'non public' and try to get all these pieces talking together I fail. I have tried multitude of different approaches. This is regularly portrayed as magic. It is wonderfully written https://gist