Error Handling and More

Sample Error	Description	Resolution
IP `34.77.XXX.XX` is not allowed to access Snowflake. Contact your local security administrator or please create a case with Snowflake Support or reach us on our support line.	This error message appears when an active Network Policy is applied to the customer account or user, and the source IP address attempting to access the account is not included in the `Allowed IP Addresses` block.	To resolve this issue, follow the steps below: 1. Contact the Snowflake Account Admin or Security Admin and provide them with the IP address displayed in the error message. 2. Request them to include the IP address in the `Allowed IP Addresses` block. 3. If you are the only Account Admin or Security Admin user for the Snowflake account, then reach out to Snowflake support for assistance.

Note:Here are the recommendations to avoid the above error.

Designate at least two Account Admin or Security Admin users for your Snowflake account.
Collaborate with your network/security teams to verify if a CIDR block range can be provided in the Allowed IP Addresses list. This approach can help avoid issues with dynamic IP addresses.

Key Pair Authentication Issues

If you created the source using Key Pair as the Authentication Type, the following are the most common causes of a failed connection. For more information about generating and registering the key pair, refer to Create a Snowflake Source and Load Data.

Issue	Cause	Resolution
The source cannot authenticate with Snowflake.	The public key is not registered against the Snowflake user, or it does not correspond to the private key that you uploaded.	Register the public key using `ALTER USER <user> ADD KEY PAIR <key_name> PUBLIC_KEY = '<key_body>';`, then compare the fingerprint reported by `DESC USER` against your local key as described in the Key Pair section.
The source cannot read the uploaded key.	The private key is encrypted, but Private Key Passphrase was left empty or contains an incorrect passphrase.	Enter the passphrase that you set when generating the key. If the key was generated with the `-nocrypt` option, leave the field empty.
The uploaded file is rejected.	The key is not in the Privacy Enhanced Mail (PEM) format using the PKCS#8 standard, or it is smaller than 2048 bits.	Regenerate the key pair using the commands in the Key Pair section, and upload the resulting `rsa_key.p8` file.
The connection stops working after it was previously fine.	The key pair was rotated or removed in Snowflake, or the key has expired.	Register the current public key against the Snowflake user and upload the matching private key to the source.

Data Ingestion Specification

Supported Regions

Currently, we support data ingestion in the following regions:

EU – All EU countries’ data are ingested to the bucket provisioned for you in the EU region
UK – United Kingdom’s data are ingested to the bucket provisioned for you in the UK region. You can find the full list of Country to Region mapping under Country to Region Mapping.

Supported PII

For raw personal identifiers (PII), we mask the PII information across the UI for all roles once you classify them in your organisation’s catalogue. Flagging the raw PII fields in your organisation’s catalogue is a critical step and is the responsibility of the organisation. The encrypted data is only available to the downstream systems for activation purposes.

Note:We use the RSA Encryption Algorithm.

​Key Pair Authentication Issues

​Data Ingestion Specification

​Supported Regions

​Supported PII

Key Pair Authentication Issues

Data Ingestion Specification

Supported Regions

Supported PII