This provides an additional option that forces connection through the private instance IP address, even if an elastic IP address is allocated. This is because (unless a NAT instance is configured) an elastic IP address is required to access the internet, but you can't route out from AWS back into a different instance on an elastic IP.
(Grabbed this diff by doing git show HEAD on the production machine, which is why there's no context)