Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • Hey Alex, welcome to the site. I like this question and wish I could answer, but I am not familiar with RDS and its limitations. I assume normal mysql replication can't be setup on RDS? Commented Dec 11, 2012 at 16:07
  • @DTest, Hi, Thanks for pointing out the shortcoming of my question - AWS RDS is very limited in what you can do. No SSH or command line access, no file system access. You cannot run normal MySQL replication (forums.aws.amazon.com/thread.jspa?threadID=46377&tstart=0) Commented Dec 11, 2012 at 16:37
  • 1
    with rolando's method for setting up the read slave, I have a question regarding "Our current process is not a “continuous” replication because of batch operations on the reporting side. " Would a dedicated read slave let you do what you want? You could always stop slave; for your reporting operations, if you needed to. Commented Dec 11, 2012 at 17:54
  • thanks for your help. i think maybe the constraints have left me with this "by hand" iterative copy as my only option. Commented Dec 12, 2012 at 15:19