# Client Connection: Google Cloud Storage

Fields with the asterisk **\*** are mandatory.

<table><thead><tr><th width="230">Properties</th><th>Description</th></tr></thead><tbody><tr><td><strong>STATUS</strong></td><td><p>Enable or disable the client connection. Possible values:</p><ul><li>Enabled (default)</li><li>Disabled</li></ul></td></tr><tr><td><strong>NAME *</strong></td><td>Name of the Google Cloud Storage connection you are creating. The maximum number of characters is 128. Blanks and the ' " | special characters are not supported.</td></tr><tr><td><strong>DESCRIPTION</strong></td><td>Description of the Google Cloud Storage connection you are creating. The maximum number of characters for this field is 2048.</td></tr><tr><td><strong>CONNECTION TIMEOUT *</strong></td><td>Number of seconds without network activity to wait before closing a session due to inactivity.<br>Default value: 60.</td></tr><tr><td><strong>SEARCH CREDENTIAL *</strong></td><td>Select the Credential - uploaded in <strong>Setup</strong> → <a href="/pages/6W1guWHnD45MCfioSgX5">Credentials</a> - to be associated with the Client Connection.</td></tr><tr><td><strong>BUCKET NAME *</strong></td><td>Enter the name of the Google Cloud Storage Service bucket. The minimum number of characters is 3 and the maximum is 63. Blanks and special characters are not supported.<br>Note that the bucket’s service account must also have the <code>roles/viewer</code> role on the Data Mover project. This role only allows it to read metadata and resources in read‑only mode, through permissions such as <code>resourcemanager.projects.get</code>.</td></tr><tr><td><strong>USE PROXY</strong> </td><td><p>Enable this toggle button to use an HTTP or HTTPS proxy. The <strong>proxyURL</strong> mandatory option will appear. Enter the proxy URL in the format: <br>- http://host:port for HTTP <br>- https://host:port for HTTPS </p><p>Optionally, select the <strong>UseProxyAuthentication</strong> toggle button. This option will set basic authentication with the specified user and password, which must be entered in the <strong>proxyUsername</strong> and <strong>proxyPassword</strong> fields.</p></td></tr><tr><td><strong>SSL AUTHENTICATION PROTOCOL</strong></td><td><p>Select the SSL authentication protocol:</p><ul><li>ALL</li><li><p>ONLY SPECIFIC VALUES:</p><ul><li>SSLv3</li><li>TLSv1</li><li>TLSv1_1</li><li>TLSv1_2</li><li>TLSv1_3</li></ul></li></ul></td></tr><tr><td><strong>ACCEPTED CIPHER SUITES</strong></td><td><p>Select the cipher suites. Possible values:</p><ul><li>ALL</li><li>ONLY SPECIFIC VALUES. See <a href="/pages/bXblCQPvaPonLHqKDwk2#accepted-cipher-suites">ACCEPTED CIPHER SUITES</a> for details.</li></ul></td></tr><tr><td><strong>MAX RETRIES *</strong></td><td>Maximum number of retries. If this field is empty or set to 0, no retries will be executed and the job will be set to Failed if the first attempt is not successful. A high value corresponds to a high number of retrying attempts.</td></tr><tr><td><strong>RETRY INTERVAL</strong></td><td>This field will appear only if you have set the maximum numbers of retries to 1 or greater.<br>Time (in seconds) waited before retrying executing a job. The lower the value, the more frequent the retrying attempts. If this field is empty or set to 0, no retries will be executed and the job will be set to Failed if the first attempt is not successful.</td></tr><tr><td><strong>CONFIGURATION TEST</strong></td><td>Use this section to test that the <strong>Cluster</strong> and the <strong>STENG</strong> are connected correctly.<br>Select a <strong>Cluster</strong> and a <strong>STENG</strong> you want to test and click the <strong>TEST</strong> button. A message with a green check will confirm a successful connection. A message with a red exclamation mark will warn about an unsuccessful connection. The message also details the reason why the connection fails.<br>The first time you try to test the connection, if trusting certificates are missing, a generic error message will appear. In this case, go to the <strong>Setup</strong> → <strong>Untrusted Cache</strong> → <strong>Certificates</strong> tab and trust the 3 Google certificates that are listed. If you now test again the connection and you see the same error message, the trust anchor file (or root file) is missing. This file must be asked to the Administrators of the Google Storage site. The file must be imported into the <strong>Setup</strong> → <strong>Trust Store</strong> → <strong>Certificates</strong> tab and clicking the <strong>Import</strong> button.<br>Information on how to trust and import certificates is available in the <a href="/pages/rlPsHn4Gn2gVhpm02iuT">Key Stores and Trust Stores</a> section of this documentation.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.primeur.com/data-mover-1.21/transfer-protocols-and-connectors/client-connections/client-connection-google-cloud-storage.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.