Egress IPs and IP-based restriction on Supabase

,
1

Hi :wave:,
To comply with SOC 2, I’m required to limit the connections to the Supabase database using IPs. I tried to allocate an egress IP for that in Fly, but I noticed the IP goes away once the service restarts. Is there a solution to that need on Fly that persists across machine restarts and deploys?

Thanks,
Pedro

2

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.