Inconsistent IP Addresses in AWS Wavelength: Discrepancy between Elastic IP and Server IP

I have recently encountered a puzzling observation while working with AWS Wavelength, specifically in nodes located in both Toronto and Tokyo. It appears that there is a discrepancy between the public IP address assigned to the Wavelength instance and the associated elastic IP address.

` I set up an AWS Wavelength node in Toronto and noticed an intriguing behavior regarding the public IP address assigned to the server. I observed that the public IP address displayed on the server differs from the elastic IP address assigned to the instance. However, I also noticed that in Wavelength instances located in Tokyo, the public IP address in the elastic IP section matches the one assigned to the server.

I would like to understand the underlying reasons behind this discrepancy and the potential network configurations involved in AWS Wavelength. Can anyone shed some light on why the Toronto Wavelength node exhibits a distinct public IP address on the server compared to the assigned elastic IP address, while the Tokyo Wavelength instances seem to align the two IP addresses?`

I'm curious about the specific factors that contribute to this variation between Wavelength nodes in different regions. If anyone has encountered a similar situation or has expertise in AWS networking, I would greatly appreciate your insights. Understanding the nuances of this behavior will help me optimize my AWS Wavelength deployments and ensure a seamless experience for my applications.