New answers tagged

0

I think is this likely because our db.m3 is not in a VPC, and db.m4 instances are required to be in a VPC.


0

in Multi AZ- can you specify what zones because those flavors are not available in all zones. The following list describes the current Amazon RDS DB instance classes and the Amazon EC2 instance type used for each: Standard – Latest Generation (db.m4) – Third generation instances that provide more computing capacity than the second generation ...


1

Cross AZ latency should be quite low (e.g. Sub <25ms) If your application queries are in series and not parallel then it will require round trip time across the AZ's (the time will be cumulative of the series). I would create an ec2 machine in the same AZ as the RDS instance and use ping between your ec2 instances to work out your base latency. Then ...


0

RDS will handle replication issue itself that's why AWS made RDS. You focus on your work while AWS takes care of all these stuff (replication, backup, failover etc.) Create read replica of your RDS instance. Read replica is considered as slave while your RDS instance which is your master is called as Primary. If you want to set up slave externally below ...


0

Here's how to do it. First ssh into the eb instance. eb ssh Then un the following command sudo /opt/elasticbeanstalk/bin/get-config environment --output YAML Alternatively --output YAML can be --output json. Or if you want you can pipe the variables into a node command like this: #!/usr/bin/env node var strings = [] process.stdin.resume() ...


2

RDS has recently added a stored procedure to accomplish this: EXEC rdsadmin.dbo.rds_modify_db_name N'<OldName>', N'<NewName>' source: http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.SQLServer.CommonDBATasks.html#Appendix.SQLServer.CommonDBATasks.RenamingDB



Top 50 recent answers are included