The sooner the better! On Sunday, April 23, 2017 at 5:30:26 PM UTC-4, Lorne Kligerman wrote: > > If a direct connection between an App Engine standard app to a GCE VM via > an internal IP address is what you're looking for, work is in progress! > When ready for testing I'll be sure to drop a note to this group. > > Cheers, > Lorne. > Product Manager - App Engine > > On Wednesday, April 19, 2017 at 11:32:26 AM UTC-7, Nicholas (Google Cloud > Support) wrote: >> >> This thread is a little dated and may not get the attention you expect. >> I'd recommend posting to a new thread and describing exactly the >> requirements you seek. When doing so, please describe the criteria you >> need met. >> >> - Would GAE being issuing request and GCE, responses? The other way >> around? Both? >> - Are requests and responses tightly coupled like HTTP >> requests/responses or more independent like tasks in task queues >> reflecting >> asynchronous requests? >> - What type of scaling would be employed for the App Engine >> component? Would the Compute Engine instances also be scaled? >> - What solutions have you tried? Any of the ones posted above? >> >> >> On Tuesday, April 18, 2017 at 11:32:37 PM UTC-4, Robert Dyas wrote: >>> >>> Has there been any progress on this? >>> >>> On Thursday, May 7, 2015 at 1:52:39 PM UTC-4, Ian Childress wrote: >>>> >>>> We (our Go dev team) want to connect our app engine apps to our compute >>>> engine apps directly using internal IP address. From my understanding >>>> through documentation and exhaustive searching, the solution is to use a >>>> public IP address. This solution requires whitelisting an entire ip block >>>> (Google's ip block for app engine). This both increases security risk as >>>> well as charges additional bandwidth. The other solution is to use a >>>> messaging service PubSub. This is fine for submitting tasks to be >>>> performed >>>> by the back end app, but it prevents the app engine from receiving the >>>> response from the compute engine. >>>> >>>> Have I missed the solution somewhere that allows for internal >>>> communication between app engine and compute engine? Using a job queue or >>>> public IP is not a replacement for an internal socket connection. >>>> >>>
-- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/e0f43ec9-f78b-4957-89ce-c48050fa05df%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
