Integrating with Amazon S3 for Targeted Data Discovery

You can integrate an Amazon's Simple Storage Service (S3) instance with OneTrust to access files in Amazon S3 to service data subject and consumer rights requests through Targeted Data Discovery (TDD).

Note:

This is currently a 6.7 preview feature. Please contact your OneTrust account executive to have it enabled for your environment.

To create credentials in OneTrust

You will need to create a cloud SDK credential in order to connect to Amazon S3. For more information on integration credentials, see Configuring Integration Credentials.

  1. On the Integrations menu, click Credentials.

    The Credentials screen appears.

  2. Click the Add New button.

    The Select System screen appears.

  3. Choose Amazon S3 from the selection field, then click the Next button.

    The Enter Credential Details screen appears.

  4. In the Connector Type field, select Cloud SDK. The screen will populate fields applicable to the cloud SDK connector type.
  5. Complete the fields. For more information, see Integrating with Amazon S3 for Targeted Data Discovery.
  6. Click the Save button.

Enter Credential Details Screen Reference



Field
Description
Credential name

Enter a name for the new credential.

Description

Enter a description for the new credential.

Application type

Select a connector type option from the following options:

  • Web app

  • Encryption

  • File share

  • Database

  • Decryption

  • Cloud SDK

Authentication method

Select the applicable authentication type required for your web app integration.

Protocol

Defaults to HTTPS.

Hostname

Enter the hostname for the credential. When a credential is associated to a workflow action, the hostname will be the default domain for this action. If a previous domain has been specified on the action, the hostname will replace that domain.

Key (Enter default headers)

Select the type of key which should be used in the header of the call made by the connection. You can add additional keys if your credential requires more than one header.

Value (Enter default headers)

Enter the value of the key which should be used in the header of the call made by the connection.

Token

Provide a token value for the credential.

Allow Mutual Transport Layer Security (mTLS)

Enable mutual transport layer security (mTLS) for all credentials using the Web App connector type to establish secure and trusted connections with external servers. This only applies to outbound connections made by actions in integration workflows which use this credential type.

For more information, see Setting Up Mutual Transport Layer Security.

Server certificate chain

Post a custom server certificate to any HTTPS credential to establish a secure and trusted connection with external systems not using a certificate issued by a trusted authority.

Test settings (recommended)

Enter an URL and test it to verify the credentials.

Classify as sensitive

Enable this setting if the credentials will be used in a sensitive workflow.

Note:

For more information, see Configuring Integration Credentials.

To create an integration workflow

You can create an integration workflow for Amazon S3 by using the custom workflow template available in the Gallery screen.

  1. On the Integrations menu, click Gallery.

    The Gallery screen appears.

  2. Navigate to the Amazon S3 system, then click on the tile.

    The Gallery Details screen appears.

  3. In the Custom Workflow block, click the Add button.


    The Create Workflow modal appears.

  4. Enter a name and description for the Amazon S3 workflow.


  5. Click the Create button.

    The Workflow Builder screen appears.

  6. You can begin building the Amazon S3 integration with relevant HTTP actions. For more information, seeIntegrating with Amazon S3 for Targeted Data Discovery.
  7. Click the Save button.

To configure the Amazon S3 workflow

Available System Actions

  1. On the Integrations menu, click Systems.

    The Systems screen appears.

  2. Select Amazon S3.

    The System Details screen appears.

  3. Navigate to the Actions tab. All available HTTP actions for managing file uploads and buckets are listed here. You can also create additional actions to support custom configurations. These will be available when you're building the workflow off the custom template.

    For more information, see the System Actions section in Getting Started with Integration Workflows.



    Action

    Description

    DELETE a bucket

    Delete a specific empty bucket within S3.

    DELETE file from bucket

    Delete a file from a specific S3 bucket.

    GET download a file

    Download a file from a bucket

    GET list of bucket objects

    Get the list of files within a specific S3 bucket.

    GET list of S3 buckets

    Get the list of buckets within S3.

    GET text file content

    Get the text content of a specific file within a specific S3 bucket.

    PUT Create a bucket

    Create a new bucket.

    PUT Create file with payload

    Add a file to a specific S3 bucket.

    PUT Upload File

    Upload a file to a S3 bucket.

Building the Workflow

  1. On the Integrations menu, click Connections.

    The Connections screen appears.

  2. Select your newly created Amazon S3 workflow.

    The Workflow Builder screen appears.

  3. The Amazon S3 workflow is seeded with only the initial Data Subject Request trigger action. Click the Add Action button to begin building a workflow for the Amazon S3 integration using the available system actions listed in Available System Actions .
    Note:

    Remember to enable any Amazon S3 action with your cloud SDK credential to authenticate the call.



  4. Click the Save button.
  5. Click the Activate button to launch the connection.

To update the data subject request workflow

  1. On the Privacy Rights Automation menu, click Workflows.

    The Workflows screen appears.

  2. Click the workflow you want to update with the Amazon S3 integration.

    The Workflow Details screen appears.

  3. Click the Edit button to enable editing.
  4. Click the System Subtask button.

    The Add System Subtask modal appears.

  5. Add a system subtask that triggers the newly created Amazon S3 integration.
    Note:

    Ensure that you enter Amazon S3 in the System field to populate the Amazon S3 integration workflow in the System Integration Workflow field.



  6. Click the Save button to close the modal.
  7. In the Workflow Details screen, click the Save button.
  8. Click the Activate button to reactivate the workflow.