Organízate con las colecciones
Guarda y clasifica el contenido según tus preferencias.
Usar un dominio personalizado con API Gateway
Puedes implementar un dominio personalizado para tu pasarela configurando el balanceo de carga de HTTP y HTTPS para la API GatewayPREVIEW. Una vez que hayas configurado el balanceador de carga HTTP(S) de tu pasarela, sigue los pasos que se indican a continuación para actualizar los registros DNS de tu dominio personalizado de forma que apunten al nuevo servicio de balanceador de carga.
También es necesario seguir estos pasos cuando se usa un balanceador de carga HTTP(S) con un certificado gestionado por Google (que requiere un dominio). Se recomienda asignar y usar una dirección IP estática cuando se usa con DNS. Las instrucciones específicas de este paso dependen de tu proveedor de DNS.
Para enviar tráfico al balanceador de carga, el registro DNS de tu dominio personalizado (por ejemplo, my-app-domain) debe apuntar a las direcciones IP del balanceador de carga.
Para encontrar la dirección IP de tu regla de reenvío global, usa este comando:
gcloud compute forwarding-rules list
Actualiza el registro A o AAAA de DNS de tu dominio para que dirija a la dirección IP del balanceador de carga. De esta forma, el tráfico que se envíe a la URL del dominio personalizado se enrutará a través del balanceador de carga. El DNS puede tardar desde unos segundos hasta varias horas en propagar este cambio al servidor DNS.
[[["Es fácil de entender","easyToUnderstand","thumb-up"],["Me ofreció una solución al problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Es difícil de entender","hardToUnderstand","thumb-down"],["La información o el código de muestra no son correctos","incorrectInformationOrSampleCode","thumb-down"],["Me faltan las muestras o la información que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-08-19 (UTC)."],[[["\u003cp\u003eConfiguring a custom domain for API Gateway involves setting up HTTP(S) Load Balancing for API Gateway.\u003c/p\u003e\n"],["\u003cp\u003eUpdating your custom domain's DNS records to point to the load balancer service is required after setting up the HTTP(S) load balancer.\u003c/p\u003e\n"],["\u003cp\u003eTo direct traffic to the load balancer, the DNS record of the custom domain must point to the load balancer's IP address(es).\u003c/p\u003e\n"],["\u003cp\u003eUpdating the domain's DNS A or AAAA record to the load balancer's IP address routes traffic through the load balancer, with DNS propagation taking varying amounts of time.\u003c/p\u003e\n"],["\u003cp\u003eUtilizing a static IP address with DNS when using an HTTP(S) Load Balancer is recommended.\u003c/p\u003e\n"]]],[],null,["# Use a custom domain with API Gateway\n====================================\n\n|\n| **Preview**\n|\n|\n| This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products and features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nA custom domain for your gateway can be implemented by configuring [HTTP(S) Load Balancing for API Gateway^PREVIEW^](/api-gateway/docs/gateway-load-balancing). Once the HTTP(S) load balancer for your gateway is set up, follow the steps below to update your custom domain's DNS records to point to the new load balancer service.\n\nThese steps are also required when using an HTTP(S) load balancer with a Google-managed certificate (which requires a domain). Allocating and using [a static IP address](https://cloud.google.com/sdk/gcloud/reference/compute/addresses/create) is recommended when used with DNS. The specific instructions for this step depend on your DNS provider.\n\nFor more information on setting up an HTTP(S) Load Balancer for API Gateway, see [Get started with HTTP(S) Load Balancing for API Gateway^PREVIEW^](/api-gateway/docs/gateway-serverless-neg)\n\n1. To send traffic to the load balancer, the DNS record of your custom domain (for example, `my-app-domain`) must point to the IP address(es) of the load balancer.\n\n To find the IP address of your global forwarding rule, use this command: \n\n ```\n gcloud compute forwarding-rules list\n ```\n2. Update your domain's DNS A or AAAA record to point\n to the load balancer's IP address so that traffic sent to the existing custom domain URL is routed through the load balancer instead. It may take as little as several seconds or as long as several hours for DNS to propagate this change to the DNS server."]]
