Private Service Connect 엔드포인트로 트래픽을 전송합니다. 엔드포인트가 서브넷에 연결되어 있는지 확인합니다.
외부 IP 주소가 있는 App Engine 인스턴스는 요구사항 없이 Private Service Connect 엔드포인트로 트래픽을 전송할 수 있습니다.
아웃바운드 연결 재설정
Google Cloud 은 기본 인프라를 업데이트하거나 다시 시작할 때 애플리케이션에서 VPC 및 인터넷으로의 연결 스트림을 종료하고 교체할 수 있습니다. 애플리케이션이 장기간 연결을 재사용하는 경우 끊어진 연결이 재사용되지 않도록 애플리케이션을 구성하여 연결을 다시 설정하는 것이 좋습니다.
App Engine 서비스 간 액세스 권한 맞춤설정
App Engine 서비스가 여러 개 있고 서비스 간에 액세스 권한을 다르게 구성하려는 경우(예: App Engine 서비스 B에서만 App Engine 서비스 A에 대한 액세스를 사용 설정하려는 경우) IAP(Identity-Aware Proxy)와 함께 App Engine을 사용하면 됩니다.
App Engine 가변형 환경: Cloud SQL 인스턴스와 동일한 VPC 네트워크에 가변형 환경 앱을 배포합니다. 이제 앱이 Cloud SQL 인스턴스의 비공개 IP 주소를 사용하여 직접 연결할 수 있어야 합니다. 자세한 내용은 App Engine 가변형 환경에서 Cloud SQL로 연결을 참조하세요.
App Engine 앱을 Cloud SQL에 연결할 때 발생하는 문제 해결
Unix 소켓을 사용하여 Cloud SQL로 이전 App Engine 표준 환경 앱을 배포할 경우 앱이 Cloud SQL 인스턴스에 연결할 수 있도록 올바르게 구성되지 않으면 몇 가지 오류 메시지가 표시될 수 있습니다. 자세한 앱 구성 단계는 App Engine 표준 환경에서 연결을 참조하세요.
다음 경고 메시지는 App Engine이 작업을 성공적으로 완료하기 위해 기존 연결 방법을 사용할 수 있었음을 나타냅니다.
CloudSQL warning: your action is needed to update your application and avoid potential disruptions. Please see https://cloud.google.com/sql/docs/mysql/connect-app-engine-standard for additional details: ...
다음 오류 메시지는 Cloud SQL 연결 작업이 성공적으로 완료되지 않았음을 나타냅니다.
Cloud SQL connection failed. Please see https://cloud.google.com/sql/docs/mysql/connect-app-engine-standard for additional details: ...
두 오류 메시지 모두 다음을 확인하여 Cloud SQL 인증 프록시가 Cloud SQL 인스턴스에 연결할 수 있도록 올바르게 구성되었는지 확인합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eThis page outlines various strategies for connecting to and from App Engine, including using Serverless VPC Access and internal IP addresses.\u003c/p\u003e\n"],["\u003cp\u003eTo connect from a Virtual Private Cloud (VPC) to App Engine using an internal IP address, you must set up Private Google Access and a Private Service Connect endpoint.\u003c/p\u003e\n"],["\u003cp\u003eApp Engine instances can connect to Cloud SQL over private IP addresses, utilizing Serverless VPC Access for the standard environment and direct VPC connection for the flexible environment.\u003c/p\u003e\n"],["\u003cp\u003eWhen working with multiple App Engine services, access permissions can be customized using App Engine with Identity-Aware Proxy (IAP).\u003c/p\u003e\n"],["\u003cp\u003eConnection issues between App Engine and Cloud SQL often stem from incorrect configuration of the Cloud SQL Auth proxy, and may require updating permissions or checking the instance connection name.\u003c/p\u003e\n"]]],[],null,["# App Engine connectivity strategies\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\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\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\n### Outbound connection resets\n\nGoogle Cloud can occasionally terminate and replace connection streams from your\napplication to both [VPC](/appengine/docs/standard/connecting-vpc)\nand the internet when updating or restarting the underlying infrastructure. If your application reuses long-lived connections, we recommend that you configure your application to\nre-establish connections to avoid the reuse of a dead connection.\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\n### Troubleshoot issues connecting an App Engine app to Cloud SQL\n\nWhen deploying an older App Engine standard environment app with Cloud SQL using Unix\nsockets, you might see a few error messages if your app isn't correctly\nconfigured to connect to a Cloud SQL instance. For detailed steps to\nconfigure your app, see [Connect from App Engine standard environment](/sql/docs/mysql/connect-app-engine-standard#configure).\n\nThe following warning message indicates that App Engine was able to fall\nback on a legacy connection method to complete the operation successfully: \n\n```\nCloudSQL warning: your action is needed to update your application and avoid potential disruptions. Please see https://cloud.google.com/sql/docs/mysql/connect-app-engine-standard for additional details: ... \n```\n\nThe following error message indicates that the operation to connect to\nCloud SQL wasn't completed successfully: \n\n```\nCloud SQL connection failed. Please see https://cloud.google.com/sql/docs/mysql/connect-app-engine-standard for additional details: ...\n```\n\nFor both error messages, check the following to ensure that the\n[Cloud SQL Auth proxy](/sql/docs/mysql/connect-admin-proxy) is correctly\nconfigured to connect to a Cloud SQL instance:\n\n- The Cloud SQL Admin API must be enabled.\n- The service account for the App Engine app must have the correct permissions.\n- The instance connection name must include the region.\n\nIf the failure message persists after troubleshooting, contact\n[Google Cloud Support](https://support.google.com/cloud/#topic=3473162)\nfor assistance."]]
