aws member discovery problem with "http-proxy"

[ahoehma]

Hello,

I would like to ask something about hz aws discovery.

I'm running an aws beanstalk application of 3 instances, on all of them I deployed a springboot with hz inside. I enabled aws member discovery via tags.

In our environment we are running our own "squid-proxies" for outgoing http-traffic and all of the sudden this proxy crashed today. And in the same time my 3 hz-member instances are stopped working as before as well. After restart the 3 hz members each of them was not able anymore to discovery the other ones. Simply by saying this

"Cannot discover nodes. Starting standalone. com.hazelcast.spi.exception.RestClientException: Failure in executing REST call ..."

Caused by "Connect timed out" inside the aws-rest-client. Could it be that my ec2 (java) "proxy-settings" influence these communications somehow?

Until yet I though these ec2-info-service calls are only local on each ec2.

Any ideas here? :D

Thanks
Andreas