Snowflake connection issues

Help
, , ,
1

This topic was automatically generated from Slack. You can find the original thread here.

Nat : I wanted to make sure Pipedream team is not having any lambda / connections-to-Snowflake issues? Wanting to make sure the following Pipedream Lambda Timeout issue is on our Snowflake db or auth side and not a Pipedream lambda issue?

I am using the default Snowflake action ( with the Snowflake API npm include) and I set up its Snowflake auth… and did not edit the action:

TIMEOUT: TIMEOUT
    at Timeout._onTimeout (/opt/nodejs/node_modules/@pipedreamhq/execution-environment/lambda_handler.js:343:23)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)

And on the previous (1st) test, (no changes to actions) I received these errors:

Unable to connect: Network error. Could not reach Snowflake.
Failed to execute statement due to the following error: Unable to perform operation using terminated connection.
This step was still trying to run code when the step ended. Make sure you promisify callback functions and await all Promises. (Reason: GetAddrInfoReqWrap, Learn more: <https://pipedream.com/docs/workflows/steps/code/async>)

Thanks.

2

Dylan Sather (Pipedream) : Hi , no known issues. Let me see if I can reproduce.

3

Nat : Thanks much Dylan.

4

Nat : If it’s a network access / firewall issue on our end (team is looking into it), whitelisting these IPs might solve it? Ie, these IPs would be related to snowflake connection lambdas? https://pipedream.com/docs/destinations/http/#ip-addresses-for-pipedream-http-requests

5

Dylan Sather (Pipedream) : I’m able to successfully execute a query using our Snowflake account. Those IP addresses are actually specific to $send.http() traffic. Traffic from workflows can be sent from any IP address in the us-east-1 region of AWS (a relatively large range).

If it helps, Snowflake’s default is to allow traffic from any IP. Network policies can be specified on a user-level basis, if you were comfortable opening up access to a specific user account tied to these workflows.

6

Nat : Thanks Dylan. So “Those IP addresses are actually specific to $send.http() traffic” = this Snowflake action does not use $send.http()? Ie, those IPs are unrelated?

7

Dylan Sather (Pipedream) : That’s correct.

8

Dylan Sather (Pipedream) : Just to make sure - in the account field of your Snowflake connected account, did you enter just a value like au12345 (just the account name portion of your hostname)?

9

Nat : No I was given a full url - I just take the account id out and try I assume yeah?

10

Dylan Sather (Pipedream) : That’s correct, Snowflake calls this the “account name”. If you were given a URL like https://au12345.snowflakecomputing.com/, you’ll need to enter just au12345 in the account field

11

Nat : Ok thanks will try… though it doesn’t look like Pipedream lets me edit the Snowflake credentials in the Accounts window?

12

Dylan Sather (Pipedream) : No, that’s a gap that we’re tracking here. If you don’t mind, go ahead and create a new connected account with the new account name.

13

Nat : Ok, will do. Thnx.

14

Nat : That was it. Just a silly credentials format issue. Ha. Thanks so much Dylan!

15

Dylan Sather (Pipedream) : Glad it was that simple!