Help - Network Discovery not working against AWS

Question

Need some urgent help. Network Discovery does not find any subnets or nodes when scanning AWS subnets. The subnets exist with plenty of nodes on them. I suspect there is some sort of blocking or filtering on the AWS side that is preventing the discovery. Can anyone advise what the requirements are for Network Discovery to work? Ports, protocols, inbound\outbound, etc.

mesverrum · Answer

Network discovery works on essentially the same ports as normal monitoring. So from your polling engine you need to have potentially snmp on udp 161 to talk to linux or network appliances, and you would need all the normal WMI ports for WMI based polled, tcp 135 from the poller to initiate but the responses come back across nearly all the ephemeral windows ports unless you modify settings in a GPO to narrow the range down.