This is a little convoluted but let me tell you what is going on.  (DO NOT FOLLOW LINKS IN THIS TEXT)

1. Fired up bugzilla AMI instance

2. Initial setup

3. Changed urlbase and sslbase to point to the public name assigned to the instance. (along with other setup) and set the redirect to SSL on connect.

So far so good.  Then I did something a bit wrong, and I could fix that - it's what came after that.

4. I assigned a new ElasticIP address to it.

Then when I connected, it correctly redirected to the wrong (old) name.

5.  ssh'd back in, edited the params file to point to the proper elastic ip names and ...

Now it gets weird.

Direct connection to https://elastic_ip_name:443 - Success

BUT if I go to http://elastic_ip_name:80 I get a security warning that it's not secure (understandable) - and it shows the right server name).  After selecting "Advanced" and "Proceed..." I end up at a jut.io login page with the url indicating that it would redirect to the https://elastic_ip_name

https://cam-cbt2722-uts-4.dev.jut.io/login?return_to=https%3A%2F%2Fec2-x...

As I was writing up this report it stopped happening.  That's a bit scary - ok, a lot scary.

Anyone ever seen this before?