I am trying to connect a go app to mongo atlas.
I need to whitelist the connecting IP
I dont want to whitelist 0.0.0.0/0
It seems that if I allocate an ipv4 to my app it still uses a different ip address for outbound traffic.
Any ideas?
I am trying to connect a go app to mongo atlas.
I need to whitelist the connecting IP
I dont want to whitelist 0.0.0.0/0
It seems that if I allocate an ipv4 to my app it still uses a different ip address for outbound traffic.
Any ideas?
Right… Ingress is distinct from egress on the Fly.io platform, , and the oldest and most highlighted (in the docs) kind of dedicated address is only for the former.
There was a recent announcement about the latter, though…
Hope this helps a little!
Added databases
I saw that but still it doesn’t seem to solve the root problem. Now we have to proxy the egress through a specific machine
You can add the wishlist tag if your post is fundamentally a feature request.
(Others have asked for a simplification of the static egress IPs, and Fly seemed broadly open to it. But they’re juggling a lot of balls in the air just now…)
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.