Are external 3rd party API calls allowed from inside a CR service by default / OOB?

[dheerajpanyam]

Show More

Are external calls to 3rd party API vendors allowed out of the box with CR service? I have a CR service with a serverless VPC connector and traffic routing set to route all traffic to VPC (maybe this is the problem??) and now all calls to any of the 3rd party APIs are failing with connection error timeout connect ETIMEDOUT.  I understand that default request timeout with a CR service is 5 mins but i increased to 10 mins although it wouldn't take 10 mins for an API call, that would be insane. Is the Traffic routing option not set correctly?

[knet · Accepted solution]

If you're routing all egress traffic through the VPC network, you then need to make sure your VPC network is set up in a way that allows calls to the internet. I believe that by default it does not. 

[dheerajpanyam]

Thanks @knet . I chose 2nd option with traffic routing which is to route only private / internal IP traffic to VPC and that seemed to have worked. My CR service can now make external 3rd party API calls.