Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit 4867f75

Browse files
Merge pull request #2356 from asplulski/main
Fix docs about permissions needed for GDI from GCP SaaS services
2 parents b2217b9 + b5c517c commit 4867f75

File tree

1 file changed

+16
-8
lines changed

1 file changed

+16
-8
lines changed

gdi/get-data-in/connect/gcp/gcp.rst

Lines changed: 16 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -55,57 +55,65 @@ For more information, refer to Google's official announcement :new-page:`Introdu
5555
<h3>Select a role for your GCP service account<a name="gcp-one" class="headerlink" href="#gcp-one" title="Permalink to this headline">¶</a></h3>
5656
</embed>
5757

58-
If you use GCP's :strong:`Project Viewer` role, you won't require any changes to your GCP setup to use Splunk Observability Cloud, and any update will be applied automatically.
58+
You can use GCP's :strong:`Viewer` role as it comes with the permissions you need for most scenarios.
5959

60-
If you want to use a more restrictive role than Project Viewer, make sure your selected role has sufficient permissions to connect to Splunk Observability Cloud, otherwise you'll get an error message when trying to connect. Review and activate any missing permissions, or change the role to Project Viewer.
61-
62-
The following table specifies the permissions required for GCP integrations:
60+
Alternatively you can create a more restrictive role using the permissions in the table:
6361

6462
.. list-table::
6563
:header-rows: 1
66-
:widths: 40 60
64+
:widths: 35 45 20
6765

6866
* - :strong:`Permission`
6967
- :strong:`Required?`
68+
- :strong:`Included in GCP's Viewer role?`
7069

7170
* - ``compute.instances.list``
7271
- Yes, if the Compute Engine service is activated
72+
- Yes
7373

7474
* - ``compute.machineTypes.list``
7575
- Yes, if the Compute Engine service is activated
76+
- Yes
7677

7778
* - ``container.clusters.list``
7879
- Yes, if the Kubernetes (GKE) service is activated
80+
- Yes
7981

8082
* - ``container.nodes.list``
8183
- Yes, if the Kubernetes (GKE) service is activated
84+
- Yes
8285

8386
* - ``container.pods.list``
8487
- Yes, if the Kubernetes (GKE) service is activated
88+
- Yes
8589

8690
* - ``monitoring.metricDescriptors.get``
8791
- Yes
92+
- Yes
8893

8994
* - ``monitoring.metricDescriptors.list``
9095
- Yes
96+
- Yes
9197

9298
* - ``monitoring.timeSeries.list``
9399
- Yes
100+
- Yes
94101

95102
* - ``resourcemanager.projects.get``
96103
- Yes, if you want to sync project metadata (such as labels)
104+
- Yes
97105

98106
* - ``serviceusage.services.use``
99107
- Yes, if you want to activate the use of a quota from the project where metrics are stored
100-
101-
* - ``serviceusage.serviceUsageConsumer``
102-
- Yes, for SQL services
108+
- No, but included in ``roles/serviceusage.serviceUsageConsumer``
103109

104110
* - ``spanner.instances.list``
105111
- Yes, if the Spanner service is activated
112+
- Yes
106113

107114
* - ``storage.buckets.list``
108115
- Yes, if the Spanner service is activated
116+
- Yes
109117

110118
.. _gcp-two:
111119

0 commit comments

Comments
 (0)