This guide will walk you through the process of creating a service account in Google Cloud Platform (GCP), enabling the necessary services, and configuring permissions so you can use it with our service.

​
Prerequisites

  • Google Cloud Account: Ensure you have a Google Cloud account. If you haven’t already, you can sign up for free at Google Cloud Console.
  • GCP Project: Have a GCP project created where you can perform the actions described below. Create a project here if needed.
  • Compute Engine Enabled: Make sure that Compute Engine is enabled in your GCP project. If it is not enabled, you can do so here.
If you need help with anything below, please let us know on Discord! 😊

​
Create a Service Account

  1. Log in to the Google Cloud Console and select your project form the drop-down menu at the top of the page.
Click the Service Accounts tab on the IAM & Admin console, and click on CREATE SERVICE ACCOUNT.
  1. Set the service account id to skypilot-v1 and click CREATE AND CONTINUE.
  1. Grant the Service Account an Owner role
On the “Grant this service account access to the project” section, click the “Select a role” dropdown. Type “Owner” into the search box and select the “Owner” role from the list. Click “Continue” to proceed.

​
Create a Key for the Service Account

  1. In Service Accounts you will see your newly-created Service Account. Click on it and navigate to the KEYS tab.
  1. Click on ADD KEY and then Create new key
  1. Choose JSON as the key type and click Create
This will download the generated key JSON file on your machine.

​
Upload the created Service Account key to Komodo

  1. In the Komodo console, navigate to the Settings page
  2. Click Connect in the GCP section and upload the Service Account key file.
And that’s it! You can now launch your workloads on GCP through Komodo! Follow this tutorial to get started.

​
FAQ

A service account is a non-personal Google Cloud account used by applications or servers to authenticate and perform automated tasks with specific permissions.
The service account will be assigned the “Owner” role, granting it full permissions across all resources in the project. This level of access is typically necessary for broad management tasks. However, if your specific use case requires more tailored permissions, please let us know on Discord! :)