How ports 2434-2436 are being used by OrientDB in distributed mode?

#1

I’m trying to run a set of 3 nodes on EC2 in distributed mode. I enabled “distribution” and added configuration for AWS Hazelcast (see below):

<>

<port auto-increment="true">2434</port>
<join>     
  <multicast enabled="false"/>
  <aws enabled="true">
    <tag-key>Name</tag-key>
    <tag-value>orientdb-server</tag-value>
  </aws>
</join>

After I launch dserver.sh on all servers I don’t see any errors until the nodes find each other and try to communicate via ports 2434-2436. The nodes are in the same security group so the issue is with OrientDB not listening on these ports. How do I make sure OrientDB activates them?

2019-04-29 22:57:05:783 INFO [10.4.31.181]:2434 [orientdb] [3.8.4] Could not connect to: /10.4.30.222:2434. Reason: SocketException[Connection timed out to address /10.4.30.222:2434] [InitConnectionTask]
2019-04-29 22:57:05:783 INFO [10.4.31.181]:2434 [orientdb] [3.8.4] Could not connect to: /10.4.26.235:2435. Reason: SocketException[Connection timed out to address /10.4.26.235:2435] [InitConnectionTask]
2019-04-29 22:57:05:783 INFO [10.4.31.181]:2434 [orientdb] [3.8.4] Could not connect to: /10.4.26.235:2434. Reason: SocketException[Connection timed out to address /10.4.26.235:2434] [InitConnectionTask]
2019-04-29 22:57:05:784 INFO [10.4.31.181]:2434 [orientdb] [3.8.4] Could not connect to: /10.4.30.222:2436. Reason: SocketException[Connection timed out to address /10.4.30.222:2436] [InitConnectionTask]
2019-04-29 22:57:05:784 INFO [10.4.31.181]:2434 [orientdb] [3.8.4] Could not connect to: /10.4.26.235:2436. Reason: SocketException[Connection timed out to address /10.4.26.235:2436] [InitConnectionTask]
2019-04-29 22:57:05:784 INFO [10.4.31.181]:2434 [orientdb] [3.8.4] Could not connect to: /10.4.30.222:2435. Reason: SocketException[Connection timed out to address /10.4.30.222:2435] [InitConnectionTask]