amazon-rds

I have followed the instructions to set up AWS and MySQL such that I should be able to sign in to mysql using mysql-client and a user (named aws_iam ) without a password, but with a token generated by awscli with the role attached to my EC2 instance. The instructions are here So what I have is: An EC2 instance with a role which allows me to generate RDS credentials An RDS instance running MySQL, with a user aws_iam which is identified by AWSAuthenticationPlugin When signed in to the EC2 instance via SSH I can run mysql -h mydb.randomstring.region.rds.amazonaws.com -u root -p and enter the

My Kubernetes cluster setup has n-tier web application running in dev and test environments on AWS. For the production environment, postgres RDS was chosen, to ensure periodic backup. While creating a postgres RDS instance, kubernetes-vpc was selected for db-subnet to keep networking stuff simple during pilot run. Also, security group selected is the same as kubernetes-minions. Following is the service and endpoint yaml: apiVersion: v1 kind: Service metadata: labels: name: pgsql-rds name: pgsql-rds spec: ports: - port: 5432 protocol: TCP targetPort: 5432 -- apiVersion: v1 kind: Endpoints

I know how to restore a pg dump into a RDS database if that dump is in my machine, but how could I do it when the dump is available at a remote location, say Amazon S3? What I want to do is something like this: pg_restore -h somedomain.us-east-1.rds.amazonaws.com -p 5432 -d databasename -U username https://s3.amazonaws.com/database.dump But of course this results in pg_restore: [archiver] could not open input file "https://s3.amazonaws.com/database.dump" Thanks for your help! If a filename is not specified, pg_restore will take data from standard input ( doc ). So, this would work: wget -O -

My node.js app gives 5xx due to connection timeouts at random times. Here's how I connect and query: var mysql = require('mysql'); var config = { host: '172.10.1.1', port: 3306, user: 'user', password: 'pwd', database: 'mydb', connectionLimit: 15, queueLimit: 30 } var poolCluster = mysql.createPool(config); var queryDB = function(query, cb) { poolCluster.getConnection(function(err, connection) { if(err) { cb(err, null); } else { connection.query(query, function (err, rows) { connection.release(); cb(err, rows); }); } }); }; Also, in another alternate version, with connection pooling disabled,

What does the backup window duration setting mean when configuring an Amazon RDS instance? Ratan Sharma If you are using automated backup for a DB instance, by enabling backups. The Backup Window time is the time in which the instance’s back up will be created. Start time : This means the time of the day you configure the backup to take place. Duration : This is the time window where back up will be taken - Default is 30 minutes. For details : http://aws.typepad.com/aws/2011/03/amazon-rds-maintenance-windows-shortened.html from Working With Backups documentaion Below is the answer for "what if

Amazon officially states: "Amazon RDS gives you access to the full capabilities of a familiar MySQL database. This means the code, applications, and tools you already use today with your existing MySQL databases work seamlessly with Amazon RDS." I don't get this. Amazon RDS is accessible via web services and there a client libraries (like the one for .Net). So if I have an existing .Net application that uses a DAL which in turn queries MySQL, how can I make the same DAL talk to the Amazon RDS (via the web services). Or am I missing something here? delfuego Amazon RDS is pure MySQL, accessible

I am using cloud formation to create a setup containing an RDS instance. I am having some difficulties creating the RDS Instance on the account of the following error: DB Subnet Group doesn't meet availability zone coverage requirement. Please add subnets to cover at least 2 availability zones. Current coverage: 1 The problem is that the entire setup is on a single AZ... what am i supposed to do? just create an extra subnet in a different AZ that has nothing in it just for the RDS? Maybe there is some way AWS can create that subnet automatically and leave me out of that mess. I don't want that