After your API is deployed, users of your API need to access it through a domain name rather than an IP address. You can either:
.endpoints.PROJECT_ID.cloud.googas the domain name (where
PROJECT_IDis your Google Cloud Platform (GCP) project ID).
- Or register your own domain name, such as
example.com, which entails:
- Configuring DNS name servers (or using Cloud DNS).
- Updating registry addresses.
- Creating and maintaining DNS records.
If you already have a DNS infrastructure, or you want to register your own domain name, see Serving an API from your domain name for more information.
This page describes how to configure Cloud Endpoints APIs to use
.endpoints.PROJECT_ID.cloud.goog as the domain
name. The configuration steps on this page are applicable for APIs using
OpenAPI running on Compute Engine, Google Kubernetes Engine, or Kubernetes.
.endpoints.PROJECT_ID.cloud.goog domain name isn't
supported for APIs running on App Engine. For APIs on App Engine, we
recommend that you use
PROJECT_ID.appspot.com as the
Endpoints service name. When you deploy the API to App Engine, a DNS entry with a
name in the format
PROJECT_ID.appspot.com is created automatically.
.cloud.goog domain is managed by Google and shared by GCP
customers. Because GCP projects are guaranteed to have a globally unique project ID,
a domain name in the format
.endpoints.PROJECT_ID.cloud.goog is unique and
can be used as the domain name for your API. Configuring the
.endpoints.PROJECT_ID.cloud.goog domain name is optional. If you prefer, you
can register your own domain name.
As a starting point, this page assumes that you have already created your Cloud Endpoints API and deployed it to Compute Engine, Google Kubernetes Engine, or Kubernetes. If you need an API for testing, you can use one of the tutorials that walk you through configuring and deploying a sample API.
The following procedure describes how to configure DNS for Cloud Endpoints
APIs that use
.endpoints.[PROJECT_ID].cloud.goog as the Endpoints
service name where
[PROJECT_ID] represents your Google Cloud Platform
(GCP) project ID. For convenience, the procedure refers to your
OpenAPI configuration file as
To configure DNS:
openapi.yaml, and add the
x-google-endpointsfield to the file as shown in the following snippet:
swagger: "2.0" host: "[API_NAME].endpoints.[PROJECT_ID].cloud.goog" x-google-endpoints: - name: "[API_NAME].endpoints.[PROJECT_ID].cloud.goog" target: "[IP_ADDRESS]"
Typically, you configure the
hostfield and the
x-google-endpoints.namefield to be the same. When you deploy your OpenAPI specification, the text specified in the
hostfield is used as the name of your Endpoints service.
[API_NAME]with the name of your API (for example,
[PROJECT_ID]with your GCP project ID.
[IP_ADDRESS]with an IPv4 address.
For example, if you deploy your Endpoints API service to a Compute Engine virtual machine instance, you can use the external IP of that virtual machine. Alternatively, if you run your code on a group of virtual machine instances (or GKE pods) behind a load balancer, you can use the IP address of the load balancer.
- Deploy your new OpenAPI specification to Service Management using the
gcloud endpoints services deploy openapi.yaml
For example, if the following is specified in an
swagger: "2.0" host: "my-cool-api.endpoints.my-project-id.cloud.goog" x-google-endpoints: - name: "my-cool-api.endpoints.my-project-id.cloud.goog" target: "192.0.2.1"
When you deploy the
openapi.yaml using the previous
Service Management creates a DNS A-record,
id.cloud.goog, which resolves to the target IP address,
192.0.2.1. You might
need to wait a few minutes for the new DNS configuration to propagate.