So this is a bit of a hack, but it's what I did in my development environment. I uninstalled GeoEvent. Then logged into the admin pages of ArcGIS Server. I changed the security settings for my site and made it HTTP only. I restarted my machine. When the machine came up it was only available on HTTP (6080). I then reinstalled GeoEvent. The default 'datastore' configuration is then on the HTTP mode rather than HTTPS. This removes the SSL handshake issue.
GeoEvent had all the configurations (inputs, processes, outputs) from the first install, but I needed to go through and refresh the rules that I had created inside of the filters. Not sure why that was, but everything reconnected and remained stable when only using a HTTP connection. I'm in the place where HTTP is good enough for this dataset.
Before implementing this workaround you MUST be sure that HTTP traffic is enough for your site and that you will be able to support it going forward. Consider that if you're using Portal then everything should be HTTPS. There are instructions relating to SSL HandShakes here:
https://community.esri.com/groups/big-data/blog/2016/07/11/troubleshooting-guide-for-arcgis-spatiote...
They didn't help me as the GEE and ArcGIS Server are one and the same machine, and I could not access geoevent manager to change any of the configuration due to the error at hand. I'd welcome advise on how to fix this properly in HTTPS mode.
