![]() Make sure “Google Cloud Storage” and “Google Cloud Storage JSON API” are enabled in Google Cloud console’s API ManagerĬreate at lea one Storage bucket in your Google cloud accountĬreate a service account and export your private key in JSON formatĪt this point, although the connection is operational, you can’t test it yet as your user hasn’t authorized DSS to access GCS on their behalf.Įach user, including you, will need to follow these steps to allow DSS to access GCP on their behalf: You want an audit in GCP of your users accessesīefore connecting to Google Cloud via DSS you will have to: You don’t want your users to access resources via DSS in GCS which they don’t have permission for ![]() Your DSS users have access to your GCP project and particularly to GCS You don’t need resources access filtering per user Your DSS users don’t have direct access to the resources in GCP DSS will be registered as an OAuth2 client, authorized to request and gain access OAuth2 connection access means DSS will use the OAuth2 protocol to access the resources in GCP. This also means that in the GCP audit logs, you won’t have a tracing of the user behind this connection. With service account credentials, DSS will be able to access all resources associated with this service account, independently of the user initiating the connection. Supported: if a file some/key exists, it takes precedence over aĭSS supports connecting to GCS using a Service Account or OAuth2. Like on a filesystem, a file and a folder with the same name are not “files” with names containing / are not supported ![]() Note Besides GCS naming guide lines GCS as a filesystem-like storage comes with a few limitations: API Node & API Deployer: Real-time APIs.Automation scenarios, metrics, and checks.Location of managed datasets and folders. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |