Collaborating Groups and Shared Workflow - AWS Nitro and ACI Apps

1.0 Introduction

This article describes the steps to create, manage, and revoke collaborating groups in Fortanix Armor platform.

A Collaborating Group in Fortanix Armor represents a collaboration established between two groups that belong to different Fortanix Armor accounts. Through this collaboration, the participating groups can securely share selected resources and work together on common workflows.

This document explains the end-to-end collaboration process, including creating collaborating groups, sharing collaboration tokens, building shared workflows, approving workflows, and managing collaboration lifecycle events.

2.0 Collaborating Groups for AWS Nitro or ACI Applications

A Fortanix Armor Identity and Access Management (IAM) collaborating group is created when groups from different Fortanix Armor accounts establish a collaboration. Through this collaboration, the groups can share resources and participate together in Fortanix Confidential Computing Manager (CCM) workflows.

In a collaborating setup:

• One group act as the consumer group and initiates the collaboration.

• One or more groups act as publisher groups and participate by contributing permitted resources.

The collaboration is represented and managed through shared workflows, which enforce controlled interaction, approval sequencing, and access restrictions between participating groups.

This section describes collaboration between three Fortanix Armor IAM groups from different Fortanix Armor accounts using a Fortanix CCM workflow that includes an ACI application and two datasets. In this example, one group acts as the consumer group, and the other two groups act as publisher groups.

3.0 Create Consumer Group

This section describes how to create consumer groups that participate in a workflow collaboration with publisher groups.

In this example, a consumer group is created in a Fortanix Armor account and initiates collaboration with publisher groups using a shared workflow. The consumer group adds an ACI application and placeholder dataset nodes to the workflow, enabling publisher groups to contribute datasets to the shared workflow.

Perform the following steps to create a consumer group for workflow-based collaboration:

1. Log in to Fortanix Armor and create a new account, for example, DemoA, or log in to an existing account. For more information on how to log in and create a new Fortanix Armor account, refer to Getting Started with Fortanix Armor.

2. On the Available Solutions page, select Identity and Access Management.

3. In the IAM user interface (UI) left navigation panel, click Groups, and then on the GROUPS tab, click ADD GROUP to create the consumer group.

4. In the Create group dialog box:

   1. Name: Enter a group name. For example, DemoA-Group1.

   2. Add description: Click this to add a description, if needed.

   3. Labels: Add one or more Key-Value labels to the group

5. Click CREATE GROUP to add a new consumer group.

3.1 Create Application

Perform the following steps to add an ACI application:

1. From the Armor Solutions drop down menu on the top navigation bar, click Confidential Computing Manager to open the CCM UI.

2. In the CCM UI left navigation panel, click Applications, and then on the ACTIVE APPLICTIONS tab, click ADD APPLICATION to add a new application.

3. In the Add Application form, select ACI, and then click NEXT to proceed to create an application.

NOTE

Ensure to select the Consumer group created in Section 3.0: Create Consumer Group.

For more information on how to create an ACI application, refer to Add Application.

The application is added for approval and appears on the ACTIVE APPLICATIONS list.

4.0 Create Publisher Groups

This section describes how to create publisher groups that participate in workflow collaboration with a consumer group.

In this example, two publisher groups are created in different Fortanix Armor accounts and contribute datasets to a shared workflow initiated by the consumer group.

Perform the following steps:

1. Create two new Fortanix Armor accounts, for example, DemoB and DemoC, or log in to an existing account. For more information on how to log in and create a new Fortanix Armor account, refer to Getting Started with Fortanix Armor.

2. Repeat Steps 2 to 5 in Section 3.0: Create Consumer Group in Fortanix Armor, to create the two new publisher groups, for example, DemoB-Group2 and DemoC-Group3.

4.1 Create Dataset

Create a dataset for the first publisher group (DemoB-Group2) to participate in the workflow collaboration.

Perform the following steps to create datasets:

1. From the Armor Solutions drop down menu on the top navigation bar, click Confidential Computing Manager to open the CCM UI.

2. In the CCM UI left navigation panel, click Dataverse, and then on the DATASETS tab, click ADD DATASET to add a new dataset.

3. In the DATASET form:

   1. Connection name: Enter a name for the dataset. For example, DatasetB.

   2. Description (Optional): Enter a short description of the dataset.

   3. Group: Select the group (DemoB-Group2) as created in Section 4.0: Create Publisher Groups in Fortanix Armor.

      1. Label Details (Optional): Add one or more key–value labels to the dataset.

   4. Location: Enter the URL where the data can be accessed.

   5. Long Description: Enter the dataset details in GitHub-flavored Markdown format or click Fetch Long Description to import the Markdown file content from an external URL. Ensure that Cross-origin resource sharing (CORS) is enabled on the external URL so that Fortanix CCM can access it. For more information, refer to the steps for AWS and Azure.

   6. Credentials: Enter the credentials required to access the data.

4. Click ADD DATASET to create the dataset.

5. Repeat Steps 1 to 4 to create another dataset, for example, DatasetC for the second publisher group DemoC-Group3.

For more information on how to create a dataset, refer to Create Datasets.

The new dataset will be added to the DATASETS list.

5.0 Generate Collaboration Token

To initiate collaboration, a consumer group must authenticate itself to a publisher group. Without authentication, a publisher group could receive unsolicited or spam collaboration requests from multiple consumer groups. To prevent this, the publisher group administrator generates a collaboration token, which serves as proof of identity for collaboration requests.

When a consumer group requests collaboration, it includes the collaboration token provided by the publisher group in the request. The publisher group then verifies the token and authenticates the consumer group before allowing the collaboration to proceed.

Perform the following steps to generate the collaboration token in Fortanix Armor IAM:

1. Go to the detailed view of DemoB-Group2 in the DemoB account.

2. Click COLLABORATE to generate a new collaboration token.

   

3. In the Collaborate dialog box, click GENERATE TOKEN to generate the token.

4. Once the token is generated, click COPY to copy the collaboration token.  

   You must share this collaboration token with the consumer group administrator to enable collaboration. The method used to share the collaboration token is outside the scope of this guide.

5. Similarly, go to the detailed view of DemoC-Group3 in the DemoC account and repeat Steps 1 to 4 to generate and copy the collaboration token for DemoC-Group3. Then, share this token with the consumer group.

6. Click Show previous tokens to view the previously generated tokens.

6.0 Create Collaborating Group

This section explains the collaboration process between the consumer group and the publisher group using the collaboration token shared by the publisher group.

Perform the following steps to create a collaborating group for workflow collaboration:

1. Open the detailed view of the consumer group, for example, DemoA-Group1, in the DemoA account.

2. Click ACCEPT TOKEN.

   

3. In the Accept token dialog box, paste the collaboration token shared by the publisher group in Section 5.0: Generate Collaboration Token.

4. Click PROCEED to initiate the collaboration request.

5. Navigate to Groups and select the COLLABORATION GROUPS tab.

6. On the CONSUMER tab, verify that the consumer group DemoA-Group1 appears associated with the publisher group DemoB-Group2.

   

7. In the Status column, observe that the collaboration request is in Pending state.

   NOTE

   The publisher group must accept the collaboration request before collaboration can begin.

8. Go to the publisher group (DemoB-Group2) and navigate to the COLLABORATION GROUPS tab.

9. On the PUBLISHER tab, verify that DemoB-Group2 shows an association request from DemoA-Group1.

   

10. Click the overflow menu for the publisher group row and click Accept to approve the collaboration request.

11. Verify that the collaboration status updates to Accepted in the publisher group view.

    

12. Return to the consumer group account (DemoA) and confirm that the collaboration status for the consumer group (DemoA-Group1) also shows Accepted.

    

13. Repeat Steps 1 to 12 to create a collaborating group between DemoA-Group1 and DemoC-Group3 using the collaboration token generated by DemoC-Group3.

    

6.1 Create Shared Workflow

After creating the collaborating groups, the consumer group administrator initiates collaboration by creating a shared workflow.

In the shared workflow, the consumer group administrator creates placeholder nodes that can be filled with various Fortanix CCM resources, such as applications, datasets, and so on. Each placeholder node is assigned to a specific publisher group, and only administrators of that publisher group can populate the placeholder nodes assigned to them.

Perform the following steps as a consumer group administrator to create a shared workflow:

1. In the CCM UI left navigation panel, click the Workflows menu item in the DemoA account.

2. On the Workflows page, click ADD WORKFLOW to create a new workflow.

3. In the Add workflow form:

   1. Name: Enter a name for the workflow.

   2. Group: Select the consumer group (DemoA-Group1) for the shared workflow.

   3. Click ADD WORKFLOW to create the shared workflow.

4. On the workflow canvas, add the application that belongs to the consumer group, DemoA-Group1 created in Section 3.1: Create Application.

5. Add a dataset placeholder node to the workflow and assign it to the publisher group, DemoB-Group2.

6. Repeat Step 5 to add another dataset placeholder node and assign it to the publisher group, DemoC-Group3.

7. Connect the application node to both dataset placeholder nodes to define the workflow data flow.

8. When you connect the application node to a dataset placeholder node, the SELECT PORTS dialog box appears.

9. From the Target port drop down list, select the appropriate port for the connection.

10. Click SELECT PORTS to confirm the connection.

11. Click SAVE DRAFT to save the workflow.

Saving the workflow as a draft makes it available to the publisher groups, allowing administrators of the assigned publisher groups to access the draft workflow in their respective accounts and populate the placeholder nodes assigned to them.

6.2 Fill the Placeholder Nodes with Actual Data

After the consumer group creates the shared workflow and assigns placeholder nodes, members of the publisher groups populate the placeholder nodes with their own resources.

Each publisher group can update only the placeholder node assigned to its group. Publisher group administrators cannot add, remove, or modify other nodes in the workflow.

Perform the following steps as a publisher group administrator:

1. Log in to the DemoB account and click the Workflows menu item in the CCM UI left navigation panel.

2. On the Workflows page, click the Draft menu item. The draft shared workflow created by the consumer group appears in the list.

3. Select the workflow and locate the placeholder node assigned to the publisher group DemoB-Group2.

4. Click the placeholder node to add the dataset.

   In the DATASET form, select the dataset created earlier in Section 4.1: Create Dataset from the list.

5. Click SAVE DRAFT to save the updated shared workflow.

6. Log in to the DemoC account and repeat Steps 1 to 5 as an administrator of the publisher group DemoC-Group3, and select the dataset created earlier in Section 4.1: Create Dataset.

After all publisher groups populate their assigned placeholder nodes, the shared workflow is complete and ready for approval.

6.3 Request Approval to Create Approved Workflow

After all publisher groups fill their assigned placeholder nodes, the shared workflow is ready for approval.

Each publisher group must review and approve the workflow before the consumer group can complete the approval process.

Perform the following steps to request and approve the shared workflow:

1. Log in to the DemoA account as a consumer group administrator.

2. In the CCM UI left navigation panel, click the Workflows menu item.

3. Click the Draft menu item and select the shared workflow for which you want to request approval.

4. Click REQUEST APPROVAL to send the approval request to all the publisher groups.

   A confirmation dialog appears. Click REQUEST APPROVAL to submit the approval request to the publisher groups.

   The workflow moves to the Pending state.

5. Go to the Pending tab to view workflows awaiting approval.

6. Log in to the DemoB account as a publisher group administrator. Navigate to the Workflows menu item and click the Pending tab.

7. Select the shared workflow from the list and click VIEW REQUEST for the shared workflow.

8. In the Approval request for creating workflow dialog box, click APPROVE.

9. Log in to the DemoC account and repeat Steps 7 and 8 to approve the workflow as an administrator of the publisher group DemoC-Group3.

10. After all publisher groups approve the workflow, log in to the DemoA account as the consumer group administrator and approve the workflow to complete the approval process.

11. In the CCM UI left navigation panel, click the Tasks menu item and locate the workflow approval request. click APPROVE to finalize the workflow approval.

12. The workflow now appears in the Approved tab.

NOTE

After a shared workflow reaches the Approved state, it cannot be modified.

To make changes, edit the workflow to create a new version using EDIT WORKFLOW as described in Create, Update, Clone, and Delete Workflows. After approval, the new version replaces the previous one.

6.4 Run the Shared Workflow

Only the consumer group administrator, who owns the workflow, can run a shared workflow. The members of the publisher groups cannot run the workflow.

Use one of the following methods to run the shared workflow:

• To run the workflow using Run in the CCM UI for an application, configure the compute cluster and Job Specification in the consumer group. For more information, refer to Run the Workflow - Web Interface - ACI Applications.  

• To run the workflow for an AWS Nitro application, refer to Run the Workflow - Web Interface - AWS Nitro Applications.

After the workflow runs, execution logs are available only to the consumer group. The members of the publisher groups cannot view the workflow execution logs.

7.0 Manage Tokens

7.1 Revoke Token

A collaboration token can be revoked by a publisher group administrator.

Revoking a collaborating token does not affect existing active collaborations between the publisher group and consumer group that were established using that token. Any existing shared workflows continue to function as expected.

7.2 Revoke Status

Perform the following steps to revoke a collaboration between a consumer group and a publisher group:

1. Navigate to the COLLABORATION GROUPS page.

2. Locate the collaboration entry you want to revoke.

3. Click the overflow menu for the corresponding row and select Revoke from the drop down menu to revoke the collaboration.

You can revoke the collaboration from either the consumer group or the publisher group.

After you revoke the collaboration, the shared workflow cannot progress, and collaboration between the groups stops.