Snowflake Key-Pair Auth Timeout in Qlik on AWS EC2
I’m moving our Qlik connection from a password user to a service user with key-pair auth. Qlik runs on an AWS EC2 instance. When I switch to the new user, the connection times out:
Cannot connect to Cloud server RetCode: SQL_ERROR SqlState: HY000 NativeError: 4 Message: [Snowflake][Snowflake] (4) REST request for URL *** failed: CURLerror (curl_easy_perform() failed) - code=28 msg='Timeout was reached' osCode=11 osMsg='Resource temporarily unavailable'.
What I’ve checked so far:
EC2 can ping and curl Snowflake’s URL over port 443
The RSA public key is uploaded in Snowflake; private key is PKCS8 PEM with no passphrase
Qlik connection string mirrors the working password-user settings which currently runs fine
Questions:
Any extra Qlik or Snowflake settings needed for key-pair auth?
Could file permissions or key format on EC2 cause a hang? - Ive done almost all checks no issues with keypair or user auth
@SHARMA-G Please let me know if you are on Qlik Replicate 2024 or above. And it's better to open a support case so that we can have a call and debug this issue.
just to add i am getting the same error with the exisitng user which is already running with pw auth. Also I am able to test connection if I first use pw user as rsa keys then switch to key-pair user. however if i try subsequent connection test i get the same error . this shows no issues with key-pair setup. And there is hardly any info on this error. I am happy to arrange something but at veru high level what your view?
just to add i am getting the same error with the exisitng user which is already running with pw auth. Also I am able to test connection if I first use pw user as rsa keys then switch to key-pair user. however if i try subsequent connection test i get the same error . this shows no issues with key-pair setup. And there is hardly any info on this error
Per @shashi_holla 's comment, please open a support case so we can involve our internal support team as needed. We do not have a way to elevate issues to them via a Community post/thread.
I am using 2025.5 version and yesterday i was sucessfully tested it I have confimed all relevant user access. however today I am getting the same error again
yes its qlik replicate 2024 i am happy to open a case but I've done few migrations now without issues on this version. the only difference I can see is I didnt stoped any tasks this time while moving keys to replicate user in ec2 instance can that be causing an issue. But then why it would sucessfully connect and if i try agains it fails with same error.
