---
title: "Inbound Connector"
slug: "fortanix-ccm-inbound-connector"
updated: 2026-07-23T05:41:05Z
published: 2026-07-23T05:41:05Z
canonical: "support.fortanix.com/fortanix-ccm-inbound-connector"
---

> ## 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 into the Fortanix CCM runtime environment. These connectors allow confidential workloads to securely 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, edit, and manage inbound connectors.

Fortanix CCM currently supports the following inbound connector types:

- **Google BigQuery** – Enables retrieval and use of data stored in Google BigQuery for further processing, analysis, or integration into Fortanix CCM workflows.

> [!NOTE]
> NOTE
> 
> Ensure that a Google BigQuery project is already configured if you want to import data from BigQuery.
- **CSV** – Enables integration of data stored in comma-separated values (CSV) files. You can access CSV data by providing a valid pre-signed URL within Fortanix CCM workflows.

> [!NOTE]
> NOTE
> 
> Ensure that you obtain a valid pre-signed URL to access the CSV data. The 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 in Fortanix CCM:

1. In the CCM UI left navigation panel, click **Dataverse** → **INBOUND CONNECTORS**, and then click **ADD INBOUND CONNECTOR** to create a new inbound connector.

![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/fortanix-confidential-computing-manager-inbound-connectors-v3.0-image-j2jcibxh.png)

**Figure 1: Add Inbound Connector**
2. In the **Add Inbound Connector** form:
  1. **Select connector type**:
    - **BigQuery**: Select this option to import data from Google BigQuery.
    - **CSV**: Select this option to import data from a CSV file.
  2. If **BigQuery** is selected:

![A screenshot of a computer  Description automatically generated](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/fortanix-confidential-computing-manager-inbound-connectors-v3.0-image-eodeue2h.png)

**Figure 2: BigQuery Project ID**

    - **Dataset name**: Enter the name of the dataset from which you want to import data.
    - **Table name**: Enter the name of the table within the specified dataset.
    - **Label Details** (Optional): Assign one or more key-value labels to the connector.
    - **Table Schema** (Optional): Click **ADD TABLE SCHEMA** to define the table schema manually. You can also click **IMPORT FROM BIGQUERY JSON** to import the table schema in JSON format from Google BigQuery.
    - **API Key**: Enter the API key (Service Account JSON) required to access the Google BigQuery service. You can either paste the API key in the text box or upload the API key file in **Raw** or **Base64** format using **UPLOAD FILE**. *For more information on how togenerate 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.
    - **Connector name**: Enter a required name for the inbound connector.
    - **Description** (Optional): Add a brief description to provide additional context if needed.
    - **Group**: Select the required Fortanix Armor IAM group name from the drop down menu to associate the connector with that group.
    - **Project ID**: Enter the ID of the Google BigQuery project.
  3. If **CSV** is selected:
    - **Connector name**: Enter a required name for the inbound connector.
    - **Description (Optional)**: Add a brief description to provide additional context if needed.
    - **Group**: Select the required Fortanix Armor IAM group name from the drop down menu to associate the connector with that group.
    - **URL**: Enter the pre-signed URL of the CSV file to import data.

> [!NOTE]
> NOTE
> 
> Ensure that you obtain a valid pre-signed URL to access the CSV data. The 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).
    - **Label Details** (Optional): Assign one or more key-value labels to categorize or identify the connector.
    - **Table Schema** (Optional): Click **ADD TABLE SCHEMA** to define the schema for the CSV data source.
3. Click **ADD INBOUND CONNECTOR** to create the inbound connector.

## 3.0 Edit the Inbound Connector

Perform the following steps to edit an inbound connector:

1. In the CCM UI left navigation panel, click **Dataverse** → **INBOUND CONNECTORS**.
2. From the list of available inbound connectors, select the connector that you want to edit. The connector details page opens, where you can review and modify the configuration.
3. Click **EDIT** to modify the connector.

> [!NOTE]
> NOTE
> 
> Alternatively, click the **Edit** icon for the required connector to modify the inbound connector.
4. Update the configuration as required.
5. Click **UPDATE INBOUND CONNECTOR** to apply the changes.

## 4.0 Inbound Connector Details Overview

### 4.1 General Tab

This tab displays general information about the inbound connector and helps you manage connector configurations effectively.

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.
  - **Group**: Specifies the Fortanix Armor IAM group to which the connector belongs.
  - **Created by**: Displays the name of the user who created the connector.
  - **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**: Displays the identifier associated with the Google BigQuery 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.
  - **Group**: Specifies the Fortanix Armor IAM group to which the connector belongs.
  - **Created by**: Displays the name of the user who created the connector.
  - **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 which the CSV data is imported.
  - **Labels**: Displays any applied labels for additional categorization or identification.

### 4.2 Table Schema Tab

This tab displays the structure of the imported or connected tables. It helps you understand the schema of the data source, which is required for writing accurate and efficient scripts. By providing visibility into the table schema, this feature helps ensure compatibility and accuracy while processing data 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**: 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**: Describes the purpose or characteristics of each column.
- **DATA ANONYMIZATION**: Specifies the anonymization method used 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 uniqueness for analysis or processing.

If **BigQuery** is selected while creating the inbound connector, you can use **IMPORT FROM BIGQUERY JSON** to import table schema details into Fortanix CCM.

![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/fortanix-confidential-computing-manager-inbound-connectors-v3.0-image-ggdpbsk8.png)

**Figure 3: IMPORT FROM BIGQUERY JSON**

Perform the following steps:

1. Go to the Google BigQuery project and copy the required table schema in JSON format.
2. In the CCM UI left navigation panel, click **Dataverse** → **INBOUND CONNECTORS**.
3. Select the required Google BigQuery inbound connector.
4. Click **EDIT** to modify the connector.
5. Go to the **TABLE SCHEMA** section.
6. Click **IMPORT FROM BIGQUERY JSON** and enter the values for table schema JSON in the provided space.
7. Click **SAVE** to apply the changes.

The table schema details are imported into Fortanix CCM successfully.

> [!NOTE]
> NOTE
> 
> When modifying the schema of the inbound connector within a 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 an inbound connector:

1. In the CCM UI left navigation panel, click **Dataverse** → **INBOUND CONNECTORS**.
2. From the list of available inbound connectors, select the connector that you want to delete.
3. Click **DELETE** to remove the connector.

> [!NOTE]
> NOTE
> 
> Alternatively, click the **Delete** icon for the required connector to remove the inbound connector.
4. Click **DELETE** to confirm the action.

## 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)