Why does the management interface attempt to access 169.254.169.254
Recently run across some logs where the management interface from our gateway pair attempts to access 169.254.169.254 over HTTP. Anyone have any ideas as to why this is occurring? After some research, this address in particular is used in AWS - however this is an on-premise gateway pair. It also doesn't help that this sits in the APIPA address space, which makes adds to the curiosity as to whether it is a misconfiguration somewhere.