Communicating Between Your Services

Region ID

The REGION_ID is an abbreviated code that Google assigns based on the region you select when you create your app. The code does not correspond to a country or province, even though some region IDs may appear similar to commonly used country and province codes. For apps created after February 2020, REGION_ID.r is included in App Engine URLs. For existing apps created before this date, the region ID is optional in the URL.

Learn more about region IDs.

You can use various methods to communicate between your App Engine services or with other services, including Google Cloud services and external applications.

The simplest approach for communicating with your App Engine service is to send targeted HTTP requests, where the URL includes the name or ID of a resource. For example, you can include the ID of a service or version that you want to target, in addition to the corresponding Google Cloud project ID:


https://VERSION-dot-SERVICE-dot-PROJECT_ID.REGION_ID.r.appspot.com

For details about targeting your services, including how to define HTTPS URLs, see How Requests are Routed. To authorize the requests between your services and other Google Cloud services, see Setting Up Authentication for Server to Server Production Applications.

To share data across databases and your App Engine app or some other external application, see Understanding Data and File Storage. In the standard environment, you can also pass requests between services and from services to external endpoints using the URL Fetch API.

Additionally, services in the standard environment that reside within the same Google Cloud project can also use one of the App Engine APIs for the following tasks:

  • Share a single memcache instance.
  • Collaborate by assigning work between services through Task Queues.

Reserved URL paths

It is not possible to use the following URL paths:

  • Paths ending with /eventlog
  • Paths starting with /_ah/
  • Some paths ending with z