Snowflake Loader Setup: SSL error

I am trying to run the snowflake loader setup, but getting an SSL error at the login step. Has anyone seen this before?

My config:

  "schema": "",
  "data": {
    "name": "Snowflake ETL config",
    "awsRegion": "us-west-1",
    "auth": {
        "roleArn": "arn:aws:iam::091040842070:role/SnowflakeLoadRole",
        "sessionDuration": 900
    "manifest": "snowplow-snowflake-manifest",
    "snowflakeRegion": "us-west-2",
    "database": "snowplowdb",
    "input": "s3://snowplow-good/",
    "stage": "snowplow_stage",
    "badOutputUrl": "s3://snowplow-transformed-s3/badrow",
    "stageUrl": "s3://snowplow-transformed-s3/stage",
    "warehouse": "snowplow_etl_wh",
    "schema": "atomic",
    "account": "cxa00000",
    "username": "snowplow_loader",
    "password": {
        "ec2ParameterStore": {
            "parameterName": "snowplow.snowflake.password"
    "maxError": 1,
    "purpose": "ENRICHED_EVENTS"

And the error I am getting:

java -jar snowplow-snowflake-loader-0.5.0.jar setup --config snowflake_etl.conf --resolver iglu_resolver_swflake.json
Setting up...
Feb 21, 2020 2:09:54 AM shadeaws.profile.path.cred.CredentialsLegacyConfigLocationProvider getLocation
WARNING: Found the legacy config profiles file at [/root/.aws/config]. Please move it to the latest default location [~/.aws/credentials].
Feb 21, 2020 2:09:55 AM net.snowflake.client.jdbc.RestRequest execute
WARNING: Exception encountered for: POST HTTP/1.1 Certificate for <> doesn't match any of the subject alternative names: [*, *]
	at net.snowflake.client.jdbc.internal.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(
	at net.snowflake.client.jdbc.internal.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(
	at net.snowflake.client.jdbc.internal.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(
	at net.snowflake.client.jdbc.internal.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(
	at net.snowflake.client.jdbc.internal.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(
	at net.snowflake.client.jdbc.internal.apache.http.impl.execchain.MainClientExec.establishRoute(
	at net.snowflake.client.jdbc.internal.apache.http.impl.execchain.MainClientExec.execute(
	at net.snowflake.client.jdbc.internal.apache.http.impl.execchain.ProtocolExec.execute(
	at net.snowflake.client.jdbc.internal.apache.http.impl.execchain.RetryExec.execute(
	at net.snowflake.client.jdbc.internal.apache.http.impl.execchain.RedirectExec.execute(
	at net.snowflake.client.jdbc.internal.apache.http.impl.client.InternalHttpClient.doExecute(
	at net.snowflake.client.jdbc.internal.apache.http.impl.client.CloseableHttpClient.execute(
	at net.snowflake.client.jdbc.internal.apache.http.impl.client.CloseableHttpClient.execute(
	at net.snowflake.client.jdbc.internal.apache.http.impl.client.CloseableHttpClient.execute(
	at net.snowflake.client.jdbc.RestRequest.execute(
	at net.snowflake.client.core.HttpUtil.executeRequestInternal(
	at net.snowflake.client.core.HttpUtil.executeRequest(
	at net.snowflake.client.core.SessionUtil.openSession(
	at net.snowflake.client.jdbc.SnowflakeConnectionV1.<init>(
	at net.snowflake.client.jdbc.SnowflakeDriver.connect(
	at java.sql/java.sql.DriverManager.getConnection(
	at java.sql/java.sql.DriverManager.getConnection(
	at com.snowplowanalytics.snowflake.loader.connection.Jdbc$.getConnection(Jdbc.scala:64)
	at com.snowplowanalytics.snowflake.loader.Initializer$.run(Initializer.scala:25)
	at com.snowplowanalytics.snowflake.loader.Main$.main(Main.scala:25)
	at com.snowplowanalytics.snowflake.loader.Main.main(Main.scala)

Feb 21, 2020 2:09:55 AM net.snowflake.client.jdbc.RestRequest execute
WARNING: Null response for request=POST HTTP/1.1

Did I mis-configure something? Or should I talk to the folks at Snowflake about this?
I’m thankful for any help!

1 Like

As an update, I’ve talked to the technical support team at Snowflake and it looks like the “long” URL ( is not supported once a short URL ( was created. That’s why I’m getting SSL errors for the long version that the Snowflake loader is using to login. They also told me that for accounts in US West, the long URL would be So it seems the Snowflake loader is not up to date with how Snowflake URLs work.

I guess more people will be affected by this in the future, so probably we need to change the config and/or the way the URL is constructed.
What would be a good way for me to fix this quickly? I guess I’d have to find the source code where the URL is constructed and then remove the region? Then build the loader myself?

1 Like

Technical support at Snowflake told me that all US West accounts are in the us-west-2 region. Therefore we should change this line in the snowflake-loader code:

if (config.snowflakeRegion == "us-west-1")
1 Like

Hi @boba,

Thank you very much for the report. As you probably already noticed in the code, you can use jdbcHost property in config to overwrite the endpoint. At the same time, I definitely agree we should update our defaults, I created a ticket to address that.

It’s a bit strange that we were not aware of this problem, none of pipelines we manage (to my knowledge) experienced this problem. Also vendors usually contact us when they deprecate a component or configuration option.


I’ve experienced the same thing. Try visiting in a browser and see the SSL certificate warning. If you proceed it’s a 403 forbidden error.

On this Snowflake docs page:

  • expand the Account name examples by region and you will see that the AWS us-west-2 region is the only region that does not include the region in the URI.

It is also mentioned in their JDBC docs:


Specifies the ID for the region where your account is located.

This parameter is no longer used because the region information, if required, is included as part of the full account name. It is documented here only for backward compatibility.

It’s a fairly recent change. I’ve experienced the same thing with Metabase’s JDBC connection to Snowflake which is at least as old as June 2019: see

I did try leaving the “snowflakeRegion” blank in my config but then the URI resolves to this invalid URI

Thanks for pointing out the jdbcHost workaround, I will try that.

UPDATE: The jdbcHost works great,
e.g. "jdbcHost": "<snowflake_account_name_goes_here>",