[adamlindsay]

While a neat solution, I feel this is going the wrong way with things. One of the primary reasons to use the cloud is to get away from SPoF. This solution is simply putting lots of sites on a single instance, which is fine, but how does the port translation work across multiple instances? We ran into this problem recently while architecting a solution for our customers and we ended up using multiple ELB's to point to multiple EC2 instances. Sure at $20/mo its probably a slightly more expensive route, but it solved all the benefits of what is being promoted here. For those that don't realize ELB's can act as SSL endpoints. I believe RackSpace allows a similar such thing. It also means that no complex port/ssl configuration occurs on the web servers, they are actually much easier to deal.

[comice]

Unlike Elastic IPs, Brightbox Cloud IPs can be mapped directly to load balancers, so you can avoid the SPoF that way (load balancers are highly-available, across zones): http://brightbox.com/#load_balancers

But we also have some other upcoming features for Cloud IPs that address this in another way :)

[adamlindsay]

Ah, that is certainly helpful. I didn't realize that.

[juzfoo]

The SaaS application that I am building will have multiple customers pointing to a load-balancer(still deciding EBS vs other options) and I am still figuring out how to get the ssl part of it set up. I like your point on keeping ELBs as the SSL end point. I haven't been able to find a definite resource explaining this. Is there anything that can be shared?

[adamlindsay]

The AWS documentation does a good job explaining the setup. As for multiple ELB's mapping to the same instances, I don't know if this is actually documented, it is just kinda known. It use to require configuration via API/CLI, but appears that the web console now even lets you do it.

http://docs.amazonwebservices.com/ElasticLoadBalancing/lates...