+1 Also need this feature.
And only after allocating an dedicated ipv4 address, i just found it only affect the incoming traffic.
1 Like
+1
We also need the same feature. We will have to look somewhere else until this is available.
1 Like
+1 in case this thread gets a response. We need a whitelist-able static egress IP for a Redshift connection.
1 Like
+1
I also just discovered that the dedicated IP is only an inbound IP. This outbound IP is something I really need for security purposes. I can not use fly until this is feature is added
1 Like
+1
+1 , Where do we stand with this feature?
+1 !
+1
+1
+1 - was struggling to understand why I wasn’t able to connect to external database regardless of my dedicated IP being whitelisted.
+1
+1 - big need, happy to pay for it.
+1 im in real need of this, is there anyone with any updates?
+1
Yeah. I think this is quite common request where external integration requires IP whitelisting and also DB requires IP white listing.
It could be one biggest reason I need to leave fly io
+1
+1
Incidentally, it looks like there’s an active flyctl branch for this now, 
…
long = `Allocate a pair of static egress IPv4 and IPv6 for a machine`
short = `Allocate static egress IPs`
usage = "allocate <machine-id>"
I.e., it would just be a matter of fly m egress-ip allocate <machine-hex-id>.
(Not every one of these branches makes it into the final flyctl, of course, but this is the first time I’ve seen it mentioned in a while…)
7 Likes
That sounds pretty promising!
I wonder how much suffering @thomas has had to endure for this to (maybe) happen 
1 Like