I'm afraid Heroku relocates processes regularly throughout its cloud in order to maintain a reliable service.
That means there isn't really a good off-the-shelf solution for this. You could consider building something like a "port knocking" system where each dyno could request access to the database automatically, but frankly, that's probably more trouble than it's worth. You could also try opening up the entire Amazon AWS IP range, but that's a pretty wide hole and there is definitely no guarantee it won't change in the future. Can't really think of any other alternatives, other than moving the database. -p On Thu, Dec 15, 2011 at 3:32 AM, Andrew Chalkley <[email protected]> wrote: > I have a client who need to connect to a legacy DB. But their firewall > needs an ip/range to allow access to their DB. > > Has anyone using Heroku had the same issue? How did you get around it? > Tunnelling the connection or using a proxy service? > > Any pointers would be greatly appreciated. > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
