--- title: "Inbound Connector" slug: "users-guide-inbound-connector-1" updated: 2026-06-26T16:26:57Z published: 2026-06-26T16:26:57Z canonical: "support.fortanix.com/users-guide-inbound-connector-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.fortanix.com/llms.txt > Use this file to discover all available pages before exploring further. # Inbound Connector ## 1.0 Introduction This article describes how to create and manage **Inbound Connectors** in Fortanix Confidential Computing Manager (CCM). An Inbound Connector enables Fortanix CCM workflows to securely import input data from external sources at runtime into the Fortanix CCM runtime environment. These connectors allow confidential workloads to access and process external datasets within a trusted execution environment. Using the **Inbound Connectors** menu item in the Fortanix CCM user interface (UI), you can create, view, update, and manage inbound data connectors. Fortanix CCM currently supports the following inbound connector types: - **Google BigQuery**: It facilitates the retrieval and utilization of data stored in BigQuery for further processing, analysis, or integration into Fortanix CCM workflows. > [!NOTE] > NOTE > > Ensure that you have a BigQuery project set up and configured if you want to fetch the data from the Google BigQuery dashboard. - **CSV**: It enables the integration of data stored in comma-separated values (CSV) files. You can utilize this connector to access the CSV file data by providing the pre-signed URL within Fortanix CCM workflows. > [!NOTE] > NOTE > > Ensure to obtain a valid and pre-signed URL for accessing the data if you want to fetch the data from a URL. This URL can be hosted on [Amazon Web Services](https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-presigned-url.html) (AWS), [Microsoft Azure](https://learn.microsoft.com/en-us/azure/storage/common/storage-sas-overview), or the [Google Cloud Platform](https://cloud.google.com/storage/docs/access-control/signed-urls) (GCP). ## 2.0 Create an Inbound Connectors Perform the following steps to create an inbound connector to the Fortanix CCM: 1. In the CCM left navigation panel, click the **Dataverse** → **Inbound Connectors menu** item, and then click **+ ADD CONNECTOR** to create an inbound connector. ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/Add-inbound-connectors.png) **Figure 1: Add New Inbound Connector** 2. On the **INBOUND CONNECTORS** dialog box, select either of the following connecter types: - **BigQuery**: Select this option if you want to import data from BigQuery . - **CSV**: Select this option if your data is in CSV format and you want to import it using this connector. 3. Click **NEXT** to proceed further. 4. On the **Inbound Connector** page: - If you have selected the **BigQuery** option in *Step 2*: 1. **Connector name**: Enter a required name for the inbound connector. 2. **Description** (Optional): Add a brief description to provide additional context if needed. 3. **Labels**: Assign one or more key-value labels to the connector. 4. **Group**: Select the required group name from the drop down menu to associate the connector with that group. 5. **Project ID**: Enter the ID of the BigQuery project. ![BigQuery-ID.png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/24338625146004.png) **Figure 2: BigQuery Project ID** 6. **Dataset name**: Enter the name of the dataset from which you want to import data. 7. **Table name**: Enter the name of the table within the specified dataset. 8. **API key**: Enter the API key (Service Account JSON) required for accessing the BigQuery service in the text box provided. You can also upload the API key in **Raw** or **Base64** format using the **browse** option. *For more information on how to generate this API key, refer to* [*Google Cloud: Create an API Key*](https://cloud.google.com/docs/authentication/api-keys#create)*.* > [!NOTE] > NOTE > > The API key cannot be viewed again after submission. - If you have selected the **CSV** option in *Step 2*: 1. **Connector name**: Enter a required name for the inbound connector. 2. **Description** (Optional): Add a brief description to provide additional context if needed. 3. **Labels**: Assign one or more key-value labels to the connector. 4. **Group**: Select the required group name from the drop down menu to associate the connector with that group. 5. **URL**: Enter the URL where the CSV file is located for importing data . > [!NOTE] > NOTE > > Ensure to obtain a valid and pre-signed URL for accessing the data if you want to fetch the data from a URL. This URL can be hosted on [Amazon Web Services](https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-presigned-url.html) (AWS), [Microsoft Azure](https://learn.microsoft.com/en-us/azure/storage/common/storage-sas-overview), or the [Google Cloud Platform](https://cloud.google.com/storage/docs/access-control/signed-urls) (GCP). 5. Click **SAVE** to create the inbound connector. The inbound data connector is now created successfully. ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/CSV-inbound-connector.png) **Figure 3: Inbound Connector Added** ## 3.0 Edit the Inbound Connector Perform the following steps to modify the details of the inbound connector: 1. In the CCM left navigation panel, click the **Inbound Connectors** menu item. 2. Locate and click the inbound connector that you wish to edit from the list of available inbound connectors. A new screen opens where you can review and edit the configuration. 3. Click **EDIT** to initiate the editing process. > [!NOTE] > NOTE > > Alternatively, you can click the ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/Overflow.png) overflow menu (three dots) for the required connector and select **EDIT INBOUND CONNECTOR** to modify the connector. 4. Update the configuration as needed. 5. After you have made the necessary edits, click **SAVE** to keep your changes. The inbound data connector is now updated successfully. ## 4.0 Inbound Connector Details Overview ### 4.1 General tab This tab offers insights into general details, enabling effective management and understanding of your connectors. The displayed fields on the screen will vary depending on the type of inbound connector created: - If a Big Query Inbound Connecter is created: - **Connector type**: Displays the type of connector, such as Google BigQuery . - **Created by**: Displays the name of the user who created the connector. - **Group**: Specifies the group to which the connector belongs. - **Created at**: Displays the timestamp when the connector was initially created. - **Last updated at**: Indicates the date and time of the last update made to the connector. - **Project ID**: Refers to the identifier associated with the project. - **Dataset Name**: Displays the name of the dataset. - **Table Name**: Displays the name of the table in the dataset associated with the connector. - **Labels**: Displays any applied labels for additional categorization or identification. - If a CSV Inbound Connecter is created: - **Connector type**: Displays the type of connector, such as CSV. - **Created by**: Displays the name of the user who created the connector. - **Group**: Specifies the group to which the connector belongs. - **Created at**: Displays the date and time when the connector was initially created. - **Last updated at**: Displays the date and time of the last update made to the connector. - **URL**: Displays the Uniform Resource Locator (URL) associated with the connector from where the CSV data file was imported. - **Labels**: Displays any applied labels for additional categorization or identification. ### 4.2 Table Schema Tab This tab allows you to access the structure of the imported or connected tables. It enables you to understand the schema of the data source, which is crucial for writing accurate and efficient scripts. By providing visibility into the table schema, this feature empowers you to develop scripts seamlessly, ensuring compatibility and accuracy in data processing within the Fortanix CCM runtime environment. After successfully creating the inbound connector, you can access this tab to add the detailed table schema elements associated with it: - **Field Name**: Displays the names of individual columns within the schema. > [!NOTE] > NOTE > > Ensure that each name is unique and not repeated to avoid potential conflicts while creating the Workflows. - **Data Type**: Determines the SQL data types associated with each column such as, integer, real, text, blob, or unsupported. - **Description**: Elaborates the purpose or characteristics of each column. - **Data anonymization**: Determines options for implementing anonymization techniques to safeguard sensitive data, - **None**: Indicates that the column undergoes no data anonymization, preserving the data in its original form. - **Hashed**: Indicates that the data is anonymized by replacing it with a hashed representation, enhancing security by masking the original values while preserving their uniqueness for analysis or processing. - **ADD ROW**: Allows you to add multiple rows for defining the individual columns in the schema. ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/Table-Schema-inbound-connector.png) **Figure 4: Add Table Schema** If you have selected the **BigQuery** option in [*Section 2.0: Create the Inbound Connector*](/v1/docs/users-guide-inbound-connector-1#20-add-the-inbound-connectors), you can use the **IMPORT FROM BIGQUERY JSON** option to import the table details in JSON format into Fortanix CCM effortlessly. ![Screenshot (211).png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/26123624103188.png) **Figure 5: Import Table Schema Details** Perform the following steps: 1. Go to the BigQuery project and copy the required tables in JSON format. 2. Go to the **Table Schema** tab of the required BigQuery Inbound Connector. 3. Click **+ TABLE SCHEMA**. 4. Click **IMPORT FROM BIGQUERY JSON** available at the end of the table. 5. In the dialog box, paste the table schema JSON in the provided space. 6. Click **IMPORT**. 7. After all the details are added, click **SAVE**. All the table details from BigQuery are imported into Fortanix CCM successfully. After you have saved the details of the table, you can either remove or modify any detail. - **DELETE**: With this feature, you can delete any column within the schema. - **EDIT**: With this feature, you can modify column properties as needed. > [!NOTE] > NOTE > > When modifying the schema of the Inbound Connector within the final or approved workflow, a new workflow copy must be created to ensure that the changes are properly reflected. ## 5.0 Delete the Inbound Connector Perform the following steps to delete the inbound connector: 1. In the CCM left navigation panel, click the **Inbound Connectors** menu item. 2. Locate and click the inbound connector that you wish to remove from the list of available inbound connectors. 3. Click **DELETE** to remove the connector. > [!NOTE] > NOTE > > Alternatively, you can click the ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/Overflow.png) overflow menu (three dots) for the required connector and select **DELETE INBOUND CONNECTOR** to delete the connector. 4. Click **DELETE** to confirm the action. The inbound data connector is now deleted successfully. ## Related - [Run the Workflow - Web Interface - Connectors and Scripts](/fortanix-ccm-run-the-workflow-web-interface-connectors-scripts.md) - [Scripts](/fortanix-ccm-scripts.md) - [AWS KMS Group Setup](/fortanix-dsm-aws-kms-cdc-group-setup.md)