MySQL on AWS: RDS vs EC2

We have recently gone through a very familiar dilemma, moving the MySQL database server of a nascent solution from a hybrid On-Premise and Azure environment to the AWS Infrastructure. Whether to go with a couple of EC2 instances and have a master-slave configuration or to go with AWS’ packaged offering for the RDBMS, viz., RDS. 
This is, in fact not a new question at all.  It would have come to any person who was getting plugged into AWS/Cloud infrastructure. Personally, for me, it was like 5th or 6th Datacenter setup in AWS. Still, the reason I had this question is, in part due to the fact that the solution I was trying to port was very nascent and was not having super high write-rate requirements.
So, in the absence of high-throughput requirements, did it really made sense to go to a full-blown RDS setup? Or is it worth the time to install, configure a 2 node cluster and write some automation scripts for backup, recovery, etc?
Question: What does RDS really offer that you cannot get with a self-configured MYSQL on RDS
Answer: It really boils down to the situation and the preference you have for control, flexibility and performance/high-availability.