Get Started with Refonte.Ai
Pro
Nucleus
If you use Google Cloud Storage to store data, if you submit tasks with attachments as `gs:` protocol URIs, rather than `http:` or `https:`, we will use the Google Cloud Storage API to fetch your data. For example, instead of sending `https://storage.googleapis.com/bucket/key`, you would send `gs://bucket/key`.
We can either fetch your data using Service Account Impersonation (preferred, more secure) or Cross-project Access.
To access Cloud Storage data in your GCP project, Refonte can impersonate a service account within that project, which has permission to access data in Cloud Storage.
To set up Service Account Impersonation:
Note that if you enable the GCP integration for your account, we will not attempt to fetch attachments from the default service account ( `backend-bucket-access@attachment-storage-243718.iam.gserviceaccount.com`) directly; the policies described in GCP IAM Access will not work.
If Service Account Impersonation is not configured, we will directly fetch attachments from your GCS bucket, using the GCP service account `backend-bucket-access@attachment-storage-243718.iam.gserviceaccount.com`. You can grant access to this service account on a per-object basis with ACLs, or on a per-bucket basis with Cloud IAMPermissions.
Please note that this authentication mechanism suffers from the confused deputy problem — a third party that can guess your S3 URLs will be able to submit tasks with your data.
Updated about 2 months ago