Comment 1 for bug 480783

A clear issue here is that if Eucalyptus generates its own SSL certificate, the tools accessing it via https won't be able to automatically trust the connection because the cert will be unsigned.

I think a good option would be to have http on 8773 and https on another port if the user has specified a simple configuration option to use a legitimate SSL certificate. This would allow for easy setup on purely private clouds, but also not prevent people from slightly exposing their setup to the internet if they wish to use an external control tool such as Landscape or RightScale.