Locally my snowflake database isnt working because of this

0
Hi all, My application uses snowflake as a database. While pushing the application to acceptance instance, we have configured the network policy for snowflake database. So it was not working for me in local. I have reached out to mendix team, they asked me to get a static IP assigned to my device which I did eventually. Still then it is generating dynamic IP only day to day. We have taken another solution where we used VM to test our application but there the performance was very slow. So what to do in this scenario? Should I ask snowflake team to reconfigure the db to the old state so that I can test it or is there any other alternate way?
asked
1 answers
0

Hi Ayman,

Based on your description, this doesn't sound like a Mendix issue anymore. It sounds like a Snowflake network policy / IP allowlisting issue.

If Snowflake has been configured to allow connections only from specific IP addresses, then working locally becomes difficult unless your local machine is using a truly static public IP.

A few observations:

  • Having a "static IP assigned to your device" is often misunderstood. Your laptop does not need a static local IP; Snowflake sees your public outbound IP, which may still change depending on your ISP, VPN, or network setup.
  • If your public IP changes regularly, Snowflake network policies will continue blocking connections.
  • The fact that the VM works suggests the VM's outbound IP is probably already included in the Snowflake allowlist.

In similar projects, I've seen teams use one of these approaches:

    • Whitelist a dedicated VPN or corporate network IPDevelopers connect through the company VPN.
    • Snowflake only trusts the VPN's outbound IP(s).
    • Use a shared development VM/jump hostLess convenient, but the IP remains predictable.
    • Have Snowflake admins maintain a Dev network policyAdd developer IPs as needed.
    • Not ideal if IPs change frequently.
    • Use a cloud-hosted Mendix environment for integration testingKeep local development separate from Snowflake integration testing.

I would not recommend removing the Snowflake network policy entirely just to support local testing, especially if the policy was introduced for security reasons.

Before asking the Snowflake team to revert the configuration, I'd verify:

  • What public IP Snowflake actually sees when you connect.
  • Whether the IP changes daily.
  • Whether you're going through a VPN, proxy, or ISP that rotates outbound addresses.

If the VM is simply slow, it may be easier to improve the VM sizing or network setup than to weaken the Snowflake security configuration.

My recommendation would be to work with the Snowflake team on a stable outbound IP solution (VPN, NAT Gateway, Bastion VM, etc.) rather than reverting the database security policy. That is usually the approach used in enterprise Mendix/Snowflake integrations.



answered