A cloud engineer needs to deploy a Cloud SQL for PostgreSQL database instance that is accessible exclusively using Private IP within an existing VPC network named `prod-vpc`. Arrange the operational steps in the correct sequential order to establish Private Service Access and provision the database instance.
- 1Allocate an internal IP address range in the `prod-vpc` network for Google private services usage.
- 2Establish a private connection between `prod-vpc` and the `servicenetworking.googleapis.com` service producer.
- 3Provision the Cloud SQL instance specifying `prod-vpc` for network connectivity and disabling public IP assignment.
- 4Create the database user and initial database schema within the newly provisioned Cloud SQL instance.
Cevap
The correct operational sequence is: First, allocate an internal IP address range in the VPC network for private services. Second, establish a private connection (VPC peering) to the service producer. Third, provision the Cloud SQL instance with private IP enabled and public IP disabled. Fourth, create the initial database and configure database users.
To set up Cloud SQL with Private IP, you must first allocate an internal IP range in your VPC network. Next, you establish a VPC peering connection to `servicenetworking.googleapis.com` using that reserved range. Once private connectivity is established, you can create the Cloud SQL instance associated with the VPC network without assigning a public IP. Finally, you create the application database and user accounts inside the instance.
Adım Adım Çözüm
Anahtar Kavram
Configuring Private Service Access for Cloud SQL Private IP connectivity