FAQ
Core FAQs
Section titled “Core FAQs”Are Snowflake v2 APIs supported?
Section titled “Are Snowflake v2 APIs supported?”Yes, the LocalStack for Snowflake supports the Snowflake v2 SQL API (/api/v2/* endpoints), as well as the legacy v1 SQL API (which is still being used by a large portion of Snowflake client libraries and SDKs)
Why are my Snowflake tests failing?
Section titled “Why are my Snowflake tests failing?”LocalStack for Snowflake is now GA. If your tests are failing, it could be due to a lack of support for certain Snowflake features. We recommend checking the function coverage to see the list of supported SQL functions and feature coverage to see the list of supported features. If you encounter any issues, you can connect with us for support.
Why does the LocalStack for Snowflake run on snowflake.localhost.localstack.cloud?
Section titled “Why does the LocalStack for Snowflake run on snowflake.localhost.localstack.cloud?”The LocalStack for Snowflake operates on snowflake.localhost.localstack.cloud. This is a DNS name that resolves to a local IP address (127.0.0.1) to make sure the connector interacts with the local APIs. In addition, we also publish an SSL certificate that is automatically used inside LocalStack, in order to enable HTTPS endpoints with valid certificates.
Note: In case you are deploying the LocalStack for Snowflake in a Kubernetes cluster or some other non-local environment, you may need to add an entry to the /etc/hosts file of any client machine or Kubernetes pod that attempts to connect to the LocalStack for Snowflake pod via the snowflake.localhost.localstack.cloud domain name.
Integration FAQs
Section titled “Integration FAQs”How do I enable detailed debug logs?
Section titled “How do I enable detailed debug logs?”You can set the SF_LOG=trace environment variable in the Snowflake container to enable detailed trace logs that show all the request/response message.
When using docker-compose then simply add this variable to the environment section of the YAML configuration file.
If you’re starting up via the localstack start CLI, then make sure to start up via the following configuration:
DOCKER_FLAGS='-e SF_LOG=trace' DEBUG=1 localstack start --stack snowflakeThe snowflake.localhost.localstack.cloud hostname doesn’t resolve on my machine, what can I do?
Section titled “The snowflake.localhost.localstack.cloud hostname doesn’t resolve on my machine, what can I do?”On some systems, including some newer versions of MacOS, the domain name snowflake.localhost.localstack.cloud may not resolve properly.
If you are encountering network issues and your Snowflake client drivers are unable to connect to the emulator, you may need to manually add the following entry to your /etc/hosts file:
127.0.0.1 snowflake.localhost.localstack.cloudWhy does the Snowflake emulator say “Unable to activate license — configure a valid auth token”?
Section titled “Why does the Snowflake emulator say “Unable to activate license — configure a valid auth token”?”This message appears specifically on the Snowflake emulator image and almost always means the auth token didn’t reach the container. Confirm the variable is present inside the container:
docker exec -it <container-id> env | grep LOCALSTACK_AUTH_TOKENIf the variable is empty inside the container, fix your .env or Compose mapping and restart.
Support FAQs
Section titled “Support FAQs”How can I get help or support with LocalStack for Snowflake?
Section titled “How can I get help or support with LocalStack for Snowflake?”If you’re experiencing an issue with LocalStack for Snowflake, read our Help & Support Guide for developers and enterprise teams.