Skip to content

Commit 1968571

Browse files
maismailkouzant
andauthored
Update docs/setup_installation/gcp/getting_started.md
Co-authored-by: Antonis Kouzoupis <kouzoupis.ant@gmail.com>
1 parent 3b14485 commit 1968571

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/setup_installation/gcp/getting_started.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ gsutil mb -p $PROJECT_ID -l US gs://$BUCKET_NAME
6464

6565

6666
## Step 3: Creating a service account for your cluster instances
67-
The cluster instances will need to be granted permission to access the storage bucket and the artifcate registry. You achieve this by creating a service account that will later be attached to the Hopsworks cluster instances. This service account should be different from the service account created in step 1, as it has only those permissions related to storing objects in a GCP bucket and docker images in an artifact registry repository.
67+
The cluster instances will need to be granted permission to access the storage bucket and the artifact registry. You achieve this by creating a service account that will later be attached to the Hopsworks cluster instances. This service account should be different from the service account created in step 1, as it has only those permissions related to storing objects in a GCP bucket and docker images in an artifact registry repository.
6868

6969
### Step 3.1: Creating a custom role for accessing storage
7070
Create a file named *hopsworksai_instances_role.yaml* with the following content:

0 commit comments

Comments
 (0)