AWS Lambda integration - Improve error message & allow for port change

[t-h-man]

Problem Statement

Currently our lambda integration is running on port 8000. If there is an another service running on that port, the user will see ERROR: bind to interface failed caused by: Address already in use (os error 98)

a) we should improve the error message to make it more informative b) we can consider allowing port switch to avoid the above issue

Solution Brainstorm

Posssible solution: a) start relay on an obscure port. b) start by default on 8000, but make it configurable via env variable (needs changes in sdk and relay, can be complicated to work on all different js frameworks.

So better go with a)

[titiloxx]

I am having that message but I do not know why. I think I am not running any service on that port

[thyming]

Also running into this issue when using the aws lambda insights layer.

[sl0thentr0py]

We will just pick an obscure port here, exposing this as config doesn't hold much value. Will update issue when fixed/shipped.

[AbhiPrasad]

@sl0thentr0py are you still taking a look at this? Cleaning up some issues for maintenance stuff so wanted to see if this should be backlogged.

[sl0thentr0py]

@AbhiPrasad it's already on our backlog, you can remove it from yours.