이 페이지에서는 비공개 IP 주소를 사용하여 PostgreSQL용 AlloyDB 인스턴스에 연결하는 방법을 간략하게 설명합니다.
비공개 IP 주소를 사용하면 데이터 트래픽이 보안 네트워크 내에 유지되고 가로채기 위험이 최소화됩니다. 리소스의 내부 IP 주소는 네트워크 내부에 있으며 인터넷에서 액세스할 수 없으므로 AlloyDB 인스턴스 액세스 범위와 잠재적 공격 표면을 효과적으로 제한합니다.
비공개 IP 연결 방법
비공개 IP를 사용하여 AlloyDB 인스턴스에 액세스하려면 비공개 서비스 액세스 또는 Private Service Connect를 선택하면 됩니다. 각 연결 방법에는 고유한 장단점이 있으므로 이 문서의 정보를 사용하여 특정 요구사항에 가장 적합한 방법을 선택하세요.
비공개 서비스 액세스
비공개 서비스 액세스는 VPC 네트워크와 PostgreSQL용 AlloyDB 인스턴스가 상주하는 기본 Google Cloud VPC 네트워크 간의 가상 프라이빗 클라우드 (VPC) 피어링 연결로 구현됩니다. 비공개 연결을 통해 VPC 네트워크의 VM 인스턴스와 액세스하는 서비스가 내부 IP 주소를 사용하여 독점적으로 통신할 수 있습니다. VM 인스턴스는 비공개 서비스 액세스를 통해 사용 가능한 서비스에 도달하기 위해 인터넷 액세스 또는 외부 IP 주소가 필요하지 않습니다.
연결을 위해 비공개 서비스 액세스를 사용하는 방법에 대한 자세한 내용은 비공개 서비스 액세스 개요를 참고하세요.
Private Service Connect
Private Service Connect를 사용하면 VPC 네트워크와 AlloyDB for PostgreSQL과 같은 Google Cloud 서비스 간에 비공개 보안 연결을 만들 수 있습니다. 다른 그룹, 팀, 프로젝트 또는 조직에 속하는 여러 VPC 네트워크에서 AlloyDB 인스턴스에 연결할 수 있습니다. AlloyDB 클러스터를 만들 때 Private Service Connect를 지원하도록 사용 설정할 수 있습니다. 클러스터 내에서 AlloyDB 인스턴스를 만들 때 VPC 네트워크의 어떤 프로젝트가 액세스할 수 있는지 지정합니다.
[[["이해하기 쉬움","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 document outlines methods for connecting to AlloyDB for PostgreSQL instances using private IP addresses, ensuring data traffic remains within a secure network.\u003c/p\u003e\n"],["\u003cp\u003eTwo primary connection methods are available: private services access, which uses VPC peering, and Private Service Connect, which allows connections from multiple VPC networks.\u003c/p\u003e\n"],["\u003cp\u003ePrivate services access is suitable for smaller-scale, single-VPC setups with minimal costs, whereas Private Service Connect is ideal for larger, multi-VPC environments requiring higher security.\u003c/p\u003e\n"],["\u003cp\u003ePrivate services access requires reserving a CIDR range and is limited to RFC 1918 IP ranges, while Private Service Connect only requires a single IP address and supports both RFC 1918 and non-RFC 1918 ranges.\u003c/p\u003e\n"],["\u003cp\u003eThe chosen private IP access method for an AlloyDB cluster cannot be changed after creation, necessitating careful consideration during the initial setup.\u003c/p\u003e\n"]]],[],null,["# Private IP overview\n\nThis page provides an overview of the ways in which you can connect to your AlloyDB for PostgreSQL instance using private IP addresses.\n\nUsing private IP addresses keeps your data traffic within a secured network and minimizes risk of interception. A resource's internal IP address, being internal to its network and inaccessible from the internet, effectively limits both its scope of accessing an AlloyDB instance and potential attack surface.\n| **Note:** If you plan to use AlloyDB along with other Google Cloud services, then you can use Terraform templates for setup and management of Google Cloud networking infrastructure. For more information, see [Simplified Cloud Networking Configuration Solutions](https://github.com/GoogleCloudPlatform/cloudnetworking-config-solutions).\n\nPrivate IP connectivity methods\n-------------------------------\n\nTo access your AlloyDB instances using private IP, you can choose\neither private services access or Private Service Connect. Since each\nconnection method offers distinct advantages and trade-offs, use the information\nin this document to choose the best approach for your specific requirements.\n| **Caution:** Once you create your AlloyDB cluster, the private IP access method cannot be changed. Therefore, careful consideration is required during the initial setup process.\n\n### Private services access\n\nPrivate services access is implemented as a Virtual Private Cloud (VPC) peering connection between your VPC network and the underlying Google Cloud VPC network where your AlloyDB for PostgreSQL instance resides. The private connection enables VM instances in your VPC network and the services that you access to communicate exclusively by using internal IP addresses. VM instances don't need Internet access or external IP addresses to reach services that are available through private services access.\n\nTo automate the setup of AlloyDB clusters with private services access using Terraform, see [Deploy AlloyDB using Terraform](https://github.com/GoogleCloudPlatform/cloudnetworking-config-solutions/blob/main/docs/AlloyDB/alloydbinstance-using-psa-accessed-from-gce.md).\n\nFor more information about using private services access for connectivity, see [Private services access overview](/alloydb/docs/about-private-services-access).\n\n### Private Service Connect\n\n[Private Service Connect](/vpc/docs/private-service-connect) lets you create private and secure connections between your VPC networks and the Google Cloud service, such as AlloyDB for PostgreSQL. You can connect to your AlloyDB instance from multiple VPC networks that belong to different groups, teams, projects, or organizations. When you create an AlloyDB cluster, you can enable it to support Private Service Connect. When creating an AlloyDB instance within the cluster, you specify which projects from your VPC network can access it.\n\nFor more information about using Private Service Connect, see [Private Service Connect overview](/alloydb/docs/about-private-service-connect) and the video [What is Private Service Connect?](https://www.youtube.com/watch?v=JAFagcQBV08).\n\nChoose between methods to use\n-----------------------------\n\nBefore you make a decision about whether to use private services access or Private Service Connect as your connection method, consider the following comparison:\n\nWhat's next\n-----------\n\n- [Private services access overview](/alloydb/docs/about-private-services-access)\n- [Private Service Connect overview](/alloydb/docs/about-private-service-connect)\n- Watch a Cloud Skills Boost video to learn how to [use private services access to provide access to producer services](https://www.cloudskillsboost.google/paths/14/course_templates/36/video/500632)."]]
