When connecting to a Looker (Google Cloud core) instance from Looker Studio Pro or Studio in Looker, you specify the Looker (Google Cloud core) instance by using either the instance URL or the instance ID, depending on the instance network configuration:
- To connect to a public IP instance, use the instance URL.
- To connect to a private IP (private services access) only instance, use the instance ID.
- To connect to a private IP (private services access) and public IP instance, use the instance URL.
- To connect to a private IP (Private Service Connect) instance, use the instance ID.
Find the Looker instance ID
To find your Looker instance ID, from the Looker Help menu, select Looker Instance ID.
Looker displays the instance ID in the following format:
projects/PROJECT_ID/locations/REGION/instances/INSTANCE_NAME
Looker will replace the variables in the previous example with your instance information, as follows:
PROJECT_ID: The name of the Google Cloud project in which you created the Looker (Google Cloud core) instance.REGION: The region in which your Looker (Google Cloud core) instance is hosted.INSTANCE_NAME: The name of your Looker (Google Cloud core) instance; it isn't associated with the instance URL.
You can copy the instance ID to your clipboard by clicking the Copy button.
Use the instance ID to connect from Looker Studio Pro or Studio in Looker
To connect to Looker from Looker Studio Pro or Studio in Looker, use the Looker connector in Looker Studio.
To connect to a Looker (Google Cloud core) private IP (private services access) only instance or a private IP (Private Service Connect) instance, enter the Looker instance ID in the Enter Looker Instance URL/ID field. Enter the entire instance ID, using the following format:
projects/PROJECT_ID/locations/REGION/instances/INSTANCE_NAME
Replace the following with your instance information:
PROJECT_ID: The name of the Google Cloud project in which you created the Looker (Google Cloud core) instance.REGION: The region in which your Looker (Google Cloud core) instance is hosted.INSTANCE_NAME: The name of your Looker (Google Cloud core) instance; it isn't associated with the instance URL.
Once connected, you will see the instance listed in the Saved Looker Instances list, and it will be listed by the full instance ID.
Add or remove a public IP connection on a private services access instance
For instances that use private services access, admins can add or remove a public IP connection. Adding or removing a public IP connection has the following effects:
- Private services access instances with a public IP connection must use the instance URL to connect to Looker. No network check is performed when data is accessed.
- Private services access instances without a public IP connection must use the instance ID to connect to Looker. Private network enforcement is in place for data access.
- Data sources that were created when a public IP connection was enabled will function only when a public IP connection is enabled. Users must reconnect to the data source if the public IP connection has been disabled.
- Data sources that were created when a public IP connection was disabled will function only when a public IP connection is disabled. Users must reconnect to the data source if the public IP connection has been enabled.
Troubleshooting
If you receive an error while trying to connect to a Looker (Google Cloud core) private IP (private services access) only instance or to a private IP (Private Service Connect) only instance or data source, you may not be on the correct network to access the instance data. Select the same network as the one being used by the instance and retry the connection.