Skip to content
This repository was archived by the owner on Dec 11, 2022. It is now read-only.

Commit 926e138

Browse files
authored
Merge pull request #182 from blackjid/patch-1
Fix GCE service account scope instructions
2 parents ecb8eb6 + dd02027 commit 926e138

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@ If Grafana is running on a Google Compute Engine (GCE) virtual machine, it is po
119119

120120
1. First of all, you need to create a Service Account that can be used by the GCE virtual machine. See detailed instructions on how to do that [here](https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances#createanewserviceaccount).
121121
2. Make sure the GCE virtual machine instance is being run as the service account that you just created. See instructions [here](https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances#using).
122-
3. Allow access to the `Stackdriver Monitoring API` scope. See instructions [here](changeserviceaccountandscopes).
122+
3. Allow access to the `BigQuery API` scope. See instructions [here](changeserviceaccountandscopes).
123123

124124
Read more about creating and enabling service accounts for GCE VM instances [here](https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances).
125125

0 commit comments

Comments
 (0)