Open bboure opened 4 years ago
I found the same thing.
the timeout URL was a concatenation of the hostname and a resolved IP:
"com.amazonaws.deepdish.http.HttpRequestException: io.netty.channel.ConnectTimeoutException: connection timed out: foo.bar.eu-west-3.elb.amazonaws.com/
:4000"
switching back to port 80 solves it.
The same thing - HTTP endpoint datasource that is hosted port 5000 cannot be used by AppSync
Has this issue any solution or workaround? i'm running in the same exact problem
We will evaluate this change in a coming release. Please 👍 if this would help you.
Any progress on this? @jpignata
any news? still can't use a custom port?
+1
+1 why there are alot of limitations? you people also removed DATA API from serverless v2, and on HTTP resolvers port is now the limitation.
+1 Given the documentation says this is possible, seems like quite a bad oversight. Very much needing to use non-80/443 ports for our platform setup.
And why has it taken over 3 years to be addressed?
I have an http endpoint that listens on port 4000 and an AppSync HTTP Datasource that points to it.
When executing a GraphQl request, the resolver times out when executing the HTTP request.
From cloudwatch:
Changing port to
80
works as expected.