Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Esta página descreve as estratégias de conectividade do App Engine
mais usadas, incluindo etapas relacionadas ao uso do acesso VPC sem servidor e endereços IP internos.
O acesso VPC sem servidor é útil ao fazer chamadas de ofertas sem servidor
do Google para uma rede de nuvem privada virtual (VPC), mas não é possível
acessar instâncias do App Engine usando um endereço IP interno.
Para se conectar ao App Engine pela rede VPC usando um
endereço IP interno sem um endereço IP externo atribuído, faça o seguinte:
Configure o Acesso privado do Google. Verifique se o serviço do App Engine usa uma sub-rede com o Acesso privado do Google ativado.
Use um endpoint do Private Service Connect. Verifique se o endpoint está conectado à
sub-rede com o Acesso privado do Google ativado.
Enviar tráfego para o endpoint do Private Service Connect. Verifique se o endpoint está conectado à sub-rede.
As instâncias do App Engine com endereços IP externos podem enviar tráfego para
os endpoints do Private Service Connect sem requisitos.
Personalizar permissões de acesso entre os serviços do App Engine
Quando você tem vários serviços do App Engine e quer configurar as permissões de acesso de maneira diferente entre os serviços (por exemplo, quer ativar o acesso ao Serviço A do App Engine apenas a partir do Serviço B do App Engine), use o App Engine com Identity-Aware Proxy (IAP).
Ambiente flexível do App Engine: implante o app do ambiente flexível na mesma rede VPC da
instância do Cloud SQL. Seu app agora pode se conectar diretamente usando
o endereço IP particular da instância do Cloud SQL. Para mais informações, consulte Como se conectar do ambiente flexível do App Engine ao Cloud SQL.
Implantar um app do App Engine em uma rede VPC compartilhada
A implantação de um aplicativo no ambiente flexível do App Engine em uma rede VPC compartilhada requer um endereço IP interno. O endereço IP interno adiciona uma rota para evitar
0.0.0.0/0.
Para instâncias com o modo IP definido como internal, faça as seguintes mudanças na rede:
Se você precisar de acesso à Internet de saída, também precisará implantar o Cloud NAT para cada região anexada às sub-redes usadas.
Conforme documentado no requisito de acesso à Internet para redes VPC, a rede precisa ter uma rota de gateway de Internet padrão ou uma rota personalizada válida com um intervalo de IP de destino que seja o mais geral (0.0.0.0/0). Se você remover essa configuração, isso poderá causar falhas na implantação ou na exibição.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-04 UTC."],[[["\u003cp\u003eApp Engine connectivity can be established from a VPC network using Private Google Access and a Private Service Connect endpoint for instances without external IP addresses.\u003c/p\u003e\n"],["\u003cp\u003eServerless VPC Access enables App Engine standard environment apps to connect to Cloud SQL using internal IP addresses, while flexible environment apps can connect directly when deployed in the same VPC network.\u003c/p\u003e\n"],["\u003cp\u003eApp Engine services can have customized access permissions, using App Engine with Identity-Aware Proxy (IAP) to enable granular control between the different App Engine services.\u003c/p\u003e\n"],["\u003cp\u003eDeploying App Engine flexible environment apps in a Shared VPC network with internal IP mode requires enabling Private Google Access, adding a compatible route and firewall rule, and potentially deploying Cloud NAT for outgoing internet access.\u003c/p\u003e\n"],["\u003cp\u003eInternal ip address mode deployment in shared VPC networks requires valid default internet gateway route or custom route with \u003ccode\u003e0.0.0.0/0\u003c/code\u003e destination ip range.\u003c/p\u003e\n"]]],[],null,["# App Engine connectivity strategies\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThis page describes commonly used App Engine connectivity\nstrategies, including steps related to using [Serverless VPC Access](/vpc/docs/serverless-vpc-access) and internal IP addresses.\n\n- [Connect from VPC to App Engine instances](#set-up-connectivity-from-vpc-to-app-engine)\n- [Connect App Engine to Cloud SQL private IP addresses](#sql-connectivity)\n- [Customize access permissions between App Engine services](#access-permissions)\n- [Deploy an App Engine app in a Shared VPC network](#internal-ip)\n\nConnect from VPC to App Engine instances\n----------------------------------------\n\nServerless VPC Access is useful when making calls from Google's\nserverless offerings to a Virtual Private Cloud (VPC) network, but you can't\naccess App Engine instances using an internal IP address.\n\nTo connect to App Engine from the VPC network using an\ninternal IP address without an assigned external IP address, do the following:\n\n1. Set up [Private Google Access](/vpc/docs/private-google-access). Ensure that the App Engine service uses a Private Google Access-enabled subnet.\n2. Use a [Private Service Connect](/vpc/docs/private-service-connect) endpoint. Ensure that the endpoint is connected to the Private Google Access-enabled subnet.\n3. Send traffic to the Private Service Connect endpoint. Ensure that the endpoint is connected to the subnet.\n\nApp Engine instances with external IP addresses can send traffic to\nPrivate Service Connect endpoints without any requirements.\n\nCustomize access permissions between App Engine services\n--------------------------------------------------------\n\nWhen you have multiple App Engine services and\nwant to configure access permissions differently between services (for example,\nyou want to enable access to App Engine Service A only from App Engine Service B), you can use\n[App Engine with Identity-Aware Proxy (IAP)](/solutions/authenticating-web-users).\n\nFor more information, see [Controlling access to websites and apps](/solutions/authenticating-web-users) and [IAP documentation](/iap/docs/authenticate-users-google-accounts).\n\nConnect App Engine to Cloud SQL private IP addresses\n----------------------------------------------------\n\nTo connect your App Engine apps to [Cloud SQL](/sql)\ninstances over private IP addresses, use one of the following options:\n\n- **App Engine standard environment** : Use the [Serverless VPC Access connector](/vpc/docs/serverless-vpc-access) to connect to Cloud SQL over internal IP addresses. For more information, see [Connecting from App Engine standard environment to Cloud SQL](/sql/docs/mysql/connect-app-engine-standard#configuring).\n- **App Engine flexible environment** : Deploy your flexible environment app in the same VPC network as your Cloud SQL instance. Your app should now be able to connect directly using Cloud SQL instance's private IP address. For more information, see [Connecting from App Engine flexible environment to Cloud SQL](/sql/docs/mysql/connect-app-engine-flexible#configuring).\n\nDeploy an App Engine app in a Shared VPC network\n------------------------------------------------\n\nDeploying an application in the App Engine flexible environment in a Shared VPC network\nrequires an internal IP address. The internal IP address adds a route to avoid\n`0.0.0.0/0`.\n\nFor instances with IP mode set to `internal`, you must make the following\nchanges to the network:\n\n- Enable [Private Google Access](/vpc/docs/private-google-access) for each subnetwork that you use.\n- Create a route compatible with [Private Google Access](/vpc/docs/private-google-access) if it doesn't already exist.\n- Create a firewall rule compatible with [Private Google Access](/vpc/docs/private-google-access) if it doesn't already exist.\n- If you need outgoing internet access, you must also deploy Cloud NAT for each region attached to subnetworks that you use.\n\nAs documented in the [internet access requirement for VPC networks](/vpc/docs/vpc#internet_access_reqs),\nthe network must have a valid default internet gateway route or custom route\nwhose destination IP range is the most general (`0.0.0.0/0`). If you remove this\nsetting, it could cause deployment or serving failures."]]
