Google Object Storage

  • Updated


This storage can be used from Web Catalogs and Version Control. 


We use workload identity federation to give access to Connecter. The steps for providing access to Connecter for a bucket are as follows:

  1. Create a Service account for Connecter.
  2. Create a Workload identity pool with all the necessary APIs enabled.
  3. Configure Workload identity federation for the as an OpenID Connect (OIDC) provider to the pool. To do this, click on the Add Provider button and add a Provider with the following setup:



4. Grant access to the service account for Connecter to the workload identity pool.
5. Create a bucket (if it’s not created). For Web Catalogs, configure the bucket to have its Public access set to Subject to object ACLs. This setting can be changed later.
6. Give access to the service account for Connecter to access the bucket. You need to give permission to Connecter to perform all necessary operations on objects inside the bucket for everything to work correctly:

      1. storage.objects.create.
      2. storage.objects.delete.
      3. storage.objects.get.
      4. storage.objects.getIamPolicy.
      5. storage.objects.list.
      6. storage.objects.setIamPolicy.
      7. storage.objects.update.
      8. storage.multipartUploads.create.
      9. storage.multipartUploads.abort.
      10. storage.multipartUploads.listParts.
      11. storage.multipartUploads.list.

7. Set up a storage provider for Google Object Storage at Connecter Suite Team Portal with the necessary credentials.

      1. Bucket Name – this is the name of your bucket.
      2. Service account id – This is the id of the service account. You can find it on the service account info page.
      3. Service account email – this is the email of the service account. You can find it on the service account info page.
      4. Audience – The audience should be constructed like this: //





Article is closed for comments.