How to Onboard GCP Account

Modified on Fri, 21 Jun at 10:54 AM

ONBOARDING PROCESS:


STEP 1:


Login to CloudDefense portal using your credentials.



From the Sidebar, navigate to Admin -> Environments.

Now Click on Add New Environment and then choose GCP provider as below.




STEP 2:

Select Single GCP Project and click Next.



Now, give this project an account name as desired, which will be used as its identifier. You can also add relevant tags, if needed. Click Next.



Now select your Organization from the drop down menu and click next.



STEP 3:

This is the final step now.


1. Create your Google Cloud service account
  • Open your Google Cloud Console

  • Go to the project you want to onboard.

  • Navigate to IAM & Admin > Service Accounts.

  • Click on Create service account at top.

  • Give the service account a unique name, then click Create and continue.

  • Add following Roles to the service account

  • - Viewer- Firebase Viewer

  • Click Continue, then Done to complete creating the service account.


2. Add CloudDefense.AI principal to this service account
  • In Google Cloud console, under the Service Accounts menu, find the service account you just created.

  • Go to the Permissions tab and click on Grant Access.

  • Copy the cloudDefense.AI principal service account ID below, and Paste it into the New Principals text box

  • cdai-service-account@cloudsec-390404.iam.gserviceaccount.com

  • Assign the role of Service Account Token Creator and click Save


3. Complete Onboarding setup
  • Now in Google Cloud console, navigate to the Service Account > Details tab. You can find the email associated with this Google service account.
    It resembles sa-name@project-id.iam.gserviceaccount.com

  • Copy this email and paste in input box in left section and click Connect Project button.


Now, just click on Connect Project and the onboarding is completed! 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article