Skip to content

Commit

Permalink
[CIS GCP] Notify the user about cloud shell editor deprecation (#5031) (
Browse files Browse the repository at this point in the history
#5093)

* Update cspm-get-started-gcp.asciidoc

* add image

* minor edits

* Update docs/cloud-native-security/cspm-get-started-gcp.asciidoc

Co-authored-by: Joe Peeples <[email protected]>

* Update docs/cloud-native-security/cspm-get-started-gcp.asciidoc

Co-authored-by: Joe Peeples <[email protected]>

* Update docs/cloud-native-security/cspm-get-started-gcp.asciidoc

---------

Co-authored-by: Benjamin Ironside Goldstein <[email protected]>
Co-authored-by: Benjamin Ironside Goldstein <[email protected]>
Co-authored-by: Joe Peeples <[email protected]>
(cherry picked from commit efe4d12)

Co-authored-by: Uri Weisman <[email protected]>
  • Loading branch information
mergify[bot] and uri-weisman authored Apr 15, 2024
1 parent 50795b7 commit 4345878
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions docs/cloud-native-security/cspm-get-started-gcp.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -59,8 +59,15 @@ For most users, the simplest option is to use a Google Cloud Shell script to aut
+
image::images/cspm-cloudshell-trust.png[The cloud shell confirmation popup]
+
NOTE: Google has deprecated its old Cloud Shell editor. If you continue to use it, you may encounter the following message:
+
image::images/cspm-cloudshell-old-editor.png[The cloud shell switch editor popup]
+
If the message appears, click **X** or **Try the new Editor** and follow the next steps. When you switch to the new editor, your context should remain unchanged.
. In Google Cloud Shell, execute the command you copied. Once it finishes, return to {kib} and wait for the confirmation of data received from your new integration. Then you can click **View Assets** to see your data.

NOTE: If you encounter any issues running the command, return to {kib} and navigate again to Google Cloud Shell.

NOTE: During Cloud Shell setup, the CSPM integration adds roles to Google's default service account, which enables custom role creation and attachment of the service account to a compute instance.
After setup, these roles are removed from the service account. If you attempt to delete the deployment but find the deployment manager lacks necessary permissions, consider adding the missing roles to the service account:
https://cloud.google.com/iam/docs/understanding-roles#resourcemanager.projectIamAdmin[Project IAM Admin], https://cloud.google.com/iam/docs/understanding-roles#iam.roleAdmin[Role Administrator].
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 4345878

Please sign in to comment.