I have a Prisma x Nextjs app hosted on Fly.io, and I want to connect it to either Supabase or Neon database that has IP allowed list configured to enhance security. Otherwise the database is open to connection from the public internet without restriction, which isn’t ideal.
However, as stated in Public Network Services · Fly Docs
We don’t offer static IPs or regional IP ranges, and we discourage the use of our outbound IPs to bypass firewalls. A Machine’s outbound IP is liable to change without notice.
But in the infra log, seems like the fly.io team is working on this feature
Steve has had a fun week. He’s working on shipping (you heard it here first) static IP address assignments for individual Fly Machines — this means Fly Machines can make direct requests to the Internet (for instance, to internal on-prem APIs) with predictable IP addresses.
Steve finished up the provisioning tooling for the fou-tunnel-and-SNAT monstrosity that we talked about last week: giving Fly Machines static IP addresses, for people who talk to IP-restricted 3rd party APIs.
Do we have an ETA for static outbound IPs? Or any other recommendation on securely connecting to external database like Supabase or Neon?
Some other alternatives I’m aware of:
- https://usefixie.com/
- In an AWS private subnet, configure AWS RDS and setup Wire Guard VPN client.