On Thursday, March 8, 2012 12:25:56 PM UTC-7, Peter van Hardenberg wrote: > > On Thu, Mar 8, 2012 at 11:21 AM, Karl wrote: > >> So, I need to connect to a SOAP API that *requires* the caller have a >> fixed IP address. We all know that heroku has two options: $100 a month for >> fixed ip ssl, or no-can-do. And I'm not convinced that the instance doing >> the calling will reveal the fixed ip anyway. >> >> So, my thought is that I could create an EC2 micro instance, give it an >> elastic IP address, and hobble together a quick sinatra app to receive >> calls from my heroku app and have it make the SOAP calls. But I would like >> this EC2 instance (not under heroku's app structure) to connect to the >> postgres db directly. I'm using the shared postgres db, but I may be >> willing to go with an add-on if it works. >> >> Is this possible, will it work? >> >> PS - yes, I know I could have the sinatra app just return the SOAP XML >> back to the heroku app, and that is my plan 'B'. But if it could talk to >> the postgres db directly, it would make the setup easier and simpler. >> > > The shared databases don't support ingress from outside the Heroku cloud, > but the production databases do. > > -p >
Thanks Peter. My client won't pony up for the $200/mo Ronin, but I wish they would. Do you have any advise on the best way to handle this task in a heroku app (API receiver requires fixed ip address)? -- You received this message because you are subscribed to the Google Groups "Heroku" group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/iFdgiF2C4SsJ. 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.
