Comment 10 for bug 1412621

It appears to me that the public IP address of the unit was placed in the replset config, which expects the port to be exposed in the security group. I'm not sure why I thought it would have inserted the private address on eth0 - but it makes sense now that I have identified it was a connectivity issue.

To add to this - a workaround was to open port 37017 in the security group for the machine. I dont like the idea its traversing all the way out to the network bridge just to come back to connect to itself - but there is a clear path forward here to make it work in this particular instance.