Closed luciano-fiandesio closed 6 years ago
Hmm, weird. But I haven't tried IPv6
Any idea if this error may be related to my change or to the high port number I'm connecting to?
How high? Though really it's only if it's low (<1024) I'd expect permissions problems; so maybe it's IPv6 then.
Do the tests pass? Perhaps try writing a new test that first creates the socket with socket.socket(socket.AF_INET6)
and then wraps it, and debug to see what the errors are. Unless of course this always works locally and never on AWS... but that would be useful to know too.
Yes, the local_test.sh
script works. It looks like AWS Lambda does not really support IPv6, but I would have expected another error, see this thread: https://forums.aws.amazon.com/thread.jspa?messageID=771807򼛟
Yes, but I fear this seems to be the case according to this SO post too.
Looks like EC2 in VPCs can do IPv6 though, so worst case you could host the Python code on this (with a minimal wrapper, or maybe Serverless AWS or something), but that's a costly way round I guess
Yeah, I will experiment with Serverless. Thanks for following up, I guess you can close the issue?
See also now #50
When launching the Lambda, I get the following error:
Please, note that I had to slightly modify the code to support IPv6 (my internet provider does not support port forwarding on IPv4...).
This is basically the line I have changed:
Any idea if this error may be related to my change or to the high port number I'm connecting to?