M2.xlarge on ec2 pricing install#

I don't like not having access to the federated storage engine. I don't like not being able to run 'top' or 'iostat' on my database server to see how the cores and drives are enjoying the load. I don't like not being able to tail the error log. I don't like not having the SUPER privilege. RDS is sexy in some ways, but you can't ultimately trust what you can't ultimately fix, because you can't get to all the moving parts. The only advantage I see in RDS compared to MySQL on EC2 are the ability to do point and click snapshots, clones, and point-in-time recovery, but these are not nearly sufficient to make up for the loss of control and flexibility and they most certainly don't justify the price being higher. but RDS, not so has pointed out are some pretty good points against it. What exactly am I missing, and what are the advantages of RDS over installing your own database on an EC2 instance? It seems like I'm probably missing something big, though, because if I were right, nobody would use RDS. Given that I'm capable of handling backups myself and that EC2 offers the same ability to scale up the instance as required that RDS does, I can't see any reason at all to use RDS instead of EC2. However, when I look at the pricing for the two options (see and ) it seems that an RDS server costs almost twice as much as an EC2 server for a box with the same specs. RDS, being a dedicated database service provided by the same company as EC2, seems like it ought to be the obviously better option.

M2.xlarge on ec2 pricing install#

I have a choice between two solutions: use Amazon RDS, or just launch a new Amazon EC2 box and install MySQL on it. We now face a need to migrate our database to its own server for one of our systems. At work, we host all our webservers on Amazon EC2 and usually have used MySQL databases installed on the same box as our Apache webserver, and communicated with them on localhost.