Connectors and Connections > Data Ingestion and Replication connection properties > Google Cloud Storage V2 connection properties
  

Google Cloud Storage V2 connection properties

Create a Google Cloud Storage V2 connection to securely read data from or write data to Google Cloud Storage files.

Connect to Google Cloud Storage V2

Let's configure the Google Cloud Storage V2 connection properties to connect to Google Cloud Storage.

Before you begin

Before you configure the Google Cloud Storage V2 Connector, complete the following prerequisite tasks:
  1. 1Ensure that you have a Google service account to access Google Cloud Storage.
  2. 2Ensure that you have the client email, project ID, and private key values for the service account. You will need to enter these details when you create a Google Cloud Storage V2 connection.
  3. 3Ensure that you have enabled the Google Cloud Storage JSON API for your service account. Google Cloud Storage V2 Connector uses the Google API to integrate with Google Cloud Storage.
  4. 4Verify that you have read and write access to the Google Cloud Storage bucket that contains the source and target files.
  5. 5When you read data from or write data to a Google Cloud Storage file in a mapping, you must have the required permissions to run the mapping successfully.
  6. 6To use the Informatica encryption method, perform the following tasks:

Connection details

The following table describes the Google Cloud Storage V2 connection properties:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
This property is not supported by Data Ingestion and Replication and the Data Access Management services.
When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
Note:
If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.
For information about how to configure and use a secrets manager, see Secrets manager configuration.
Runtime Environment
The name of the runtime environment where you want to run tasks.
For database ingestion and replication tasks that have a supported source type, you can use the serverless runtime environment. You cannot run an application ingestion and replicationtask, a database ingestion and replication task, or a streaming ingestion and replication task on a Hosted Agent or elastic runtime environment.
Service Account ID
The client_email value from the Google service account key JSON file.
Service Account Key
The private_key value from the Google service account key JSON file.
To use the private key from the JSON file, enter the entire block of text found within the double quotation marks in the private_key field, starting with -----BEGIN PRIVATE KEY-----\n and ending at -----END PRIVATE KEY-----\n.
Project ID
The project_id value from the Google service account key JSON file.
If you have created multiple projects with the same service account, enter the ID of the project that contains the dataset that you want to connect to.
Optimize Object Metadata Import
Imports metadata for the selected object without parsing other objects, folders, or sub-folders available in the bucket.
This approach enhances performance by reducing the overhead and time taken to parse each object available in the bucket.
Default is not selected.
This property does not apply to a file ingestion and replication task.

Advanced settings

The following table describes the advanced connection properties:
Property
Description
Service Account Private Key ID
The private_key_id value from the Google service account key JSON file.
This property applies only to a database ingestion and replication or streaming ingestion and replication task.
Service Account Client ID
The client_id value from the Google service account key JSON file.
This property applies only to a database ingestion and replication or streaming ingestion and replication task.
Is Encrypted File
Specifies whether a file is encrypted. Select this option when you import an encrypted file from Google Cloud Storage.
Default is not selected.
Bucket Name
The Google Cloud Storage bucket name that you want to connect to.
When you select a source object , the Package Explorer lists files and folders available in the specified Google Cloud Storage bucket.
If you do not specify a bucket name, you can select a bucket from the Package Explorer to select a source.

Proxy server settings

If your organization uses an outgoing proxy server to connect to the Internet, the Secure Agent connects to Informatica® Intelligent Data Management Cloud™ (IDMC) through the proxy server.
You can configure the Secure Agent to use the proxy server on Windows and Linux. You can use the unauthenticated or authenticated proxy server.
To configure the proxy settings for the Secure Agent, perform the following tasks:

Configure proxy settings for NTLM authentication

You can use a proxy server that uses NTLM authentication to connect to Google Cloud Storage.
To configure the proxy settings for NTLM authentication, perform the following steps:
  1. 1In Administrator, select Runtime Environments.
  2. 2Select the Secure Agent for which you want to configure from the list of available Secure Agents.
  3. 3In the upper-right corner, click Edit.
  4. 4In the System Configuration Details section, select the Type as DTM for the Data Integration Server.
  5. 5Edit the JVMOption1 and add the following value:
  6. -Dhttp.auth.ntlm.domain=<domain name>
  7. 6Select the Type as Platform for the Data Integration Server.
  8. 7Edit the INFA_DEBUG property and add the following value:
  9. -Dhttp.auth.ntlm.domain=<domain name>
  10. 8Click Save.
  11. 9Restart the Secure Agent.