AWS Lambda connection resets and link local address in logging
15 or 20 times a day we see an error like the one below on our lambda instance.
One thing that jumps out is that the source address is a link local address instead
of a normal private (or public) address. Is that normal for lambas to try and use
a link local address as source to their destinations?
There appear to be no network error over DX, no bandwidth problems and thousands
of other connections per hour are successful. It's this small subset we're trying to figure out.
read tcp 169.254.176.149:58672->10.
One thing that jumps out is that the source address is a link local address instead
of a normal private (or public) address. Is that normal for lambas to try and use
a link local address as source to their destinations?
There appear to be no network error over DX, no bandwidth problems and thousands
of other connections per hour are successful. It's this small subset we're trying to figure out.
read tcp 169.254.176.149:58672->10.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.