I have two questions:
1-If you mean having only one RDS instance, there is no point in load balancing requests in front of it. If you mean having more than one RDS instance, it does not make much sense as well to load balance requests, because your database servers will most likely have different data in a given point of time. The only exception that I can see to this rule is if you have read-only RDS instances. In this case, you can probably benefit of having ELB(s) in front of them. If your application is write-intensive, you should stick with a larger RDS instance or move to a noSQL database. Don't try to load balance requests to a read/write DMBS, because you will have to deal with synchronization and a lot of other (non-trivial) aspects by yourself.
2-Yes, this is totally feasible. For web servers, of course. Not for DBMSs in general.
In spite of all the reasons for attaching ELB to RDS, AWS does not provide feature to connect ELB to RDS currently. ELB work with EC2 instances only yet.
Yes/No, you can install Different services on a EC2 instance but you can't install Same services that have different port on a EC2 instance. ELB load balance Same service to Same ports, but it can provide multiple services on an ELB. It also provide only one health check feature so if one service is dead that is point of health check, all the other services will be blocked by ELB at the same time.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With