Hardware and Software Requirements

The prerequisites for each Tetra Data Platform (TDP) component are listed in the documentation for those components. For quick reference, the following sections provide links to each component's hardware and software requirements:

TDP Requirements

To deploy the TDP, you must meet the following prerequisites:

  • Any of the latest two versions of the following web browsers:
    • Google Chrome
    • Microsoft Edge
      📘

      NOTE

      Mozilla Firefox works with most TDP features, but isn't fully supported. If you try to use the Download selected files action in Firefox, it won't work. You must use Google Chrome or Microsoft Edge to download selected files instead.

  • All of the resources, permissions, and connectivity requirements listed in AWS Deployment Requirements.

Important Considerations for Customer-Hosted Deployments

📘

NOTE

For new TDP environments, TetraScience no longer supports customer-hosted deployments. For more information about managing legacy, customer-hosted TDP deployments, see the following resources in the TetraConnect Hub:

For access, see Access the TetraConnect Hub.

For customer-hosted deployments, keep in mind the following:

  • If the private subnets where the TDP is deployed are restricted and don't have outbound access to the internet, your VPC must have specific endpoints enabled. For details, see VPC endpoints.

  • Workflows may get stuck and not process files in TDP environments that use EnvironmentSize size settings configured to either Large or X-Large and have limited IP addresses (~1,024 or less) available in their Amazon Virtual Private Cloud (VPC) subnets. Small subnets restrict the capacity for concurrent Amazon Elastic Container Service (Amazon ECS) tasks and other TDP AWS resources that require private IP addresses. To mitigate the risk, customers should work with their customer account leader to expand their available IP address pool. Our engineering team will help you do one of the following:

    • Add an additional CIDR (IPv4 /20 or larger) to the TDP's existing VPC, including two or more new subnets (IPv4 /21 or larger)

    - or -

    • Create a new VPC in the same TDP AWS account and AWS Region that has two or more subnets, each with /21 masks or larger.

Tetra Hub Requirements

The following links show the prerequisites for each Tetra Hub version:

Tetra Agent Requirements

The prerequisites for each Tetra Agent are provided in the documentation for each Agent version. For a list of Supported Agents and links to their documentation, see Supported Tetra Agents.

Tetra Connector Requirements

The prerequisites for each Tetra Connector are provided in the documentation for each Connector. For a list of supported Connectors and links to their documentation, see Supported Tetra Connectors.

TetraScience SDK Requirements

Before you can use the TetraScience Software Development Kit (SDK) to create a self-service Tetra Data pipeline (SSP), you must meet the requirements listed in SSP Setup and Prerequisites.

Network Port Requirements

The following network ports are typically opened for the TDP, but may differ for each TDP deployment based on customers' specific networking requirements.

SourceDestinationIP ProtocolProtocol/Port
On-premises instrumentsTetra File-Log AgentTCPsmb/445
All Tetra Agent hostsTDP and AWSTCPhttps/443 and https/3128
Tetra Unicorn Agent hostsUnicornTCPOPC HDA/135
Tetra LabX Agent hostsLabX ServerTCPhttp/51155 and https/51156
Tetra Data HubSee Tetra Data Hub Allow List EndpointsTCPhttps/443
Admin User and Employee WorkstationsTDP user interfaceTCPhttps/443 (SAML Optional)
Tetra HubSee Tetra Hub Allow List EndpointsTCPhttps

Documentation Feedback

Do you have questions about our documentation or suggestions for how we can improve it? Start a discussion in TetraConnect Hub. For access, see Access the TetraConnect Hub.

📘

NOTE

Feedback isn't part of the official TetraScience product documentation. TetraScience doesn't warrant or make any guarantees about the feedback provided, including its accuracy, relevance, or reliability. All feedback is subject to the terms set forth in the TetraConnect Hub Community Guidelines.