NI has validated and continuously tests supported cloud providers in relevant environments for production workloads.

Use the recommended configurations described in this manual to ensure your environment adheres to the architecture and configurations tested and supported by NI.

  • Amazon Web Services (AWS)
  • Microsoft Azure
  • AWS GovCloud (US)
  • Azure Government

Deployments with additional security constraints or specialized configurations, such as deploying with OpenShift, are evaluated on a case-by-case basis. Contact NI support for assistance with these scenarios.

Government Cloud Considerations

AWS GovCloud (US) and Azure Government are isolated sovereign cloud environments designed for U.S. government workloads subject to compliance requirements such as FedRAMP, and DoD IL standards. SystemLink Enterprise supports deployment in these environments with the following considerations.

  • Physical and logical isolation: These regions are physically and logically isolated from standard commercial regions. As a result, some services might be unavailable, have reduced feature sets, or use region-specific endpoints. Verify service availability before deployment.
  • FIPS: Both AWS GovCloud (US) and Azure Government use FIPS-approved cryptographic modules for all service API endpoints. If your compliance requirements mandate FIPS-validated encryption, ensure that all client tooling and Kubernetes configurations interact with the respective government cloud endpoints exclusively. Note that SystemLink Enterprise itself is not FIPS-compliant. Contact NI support if your workload requires end-to-end FIPS compliance.
  • OpenShift on AWS GovCloud (US): AWS GovCloud does not support the AWS Load Balancer Operator that OpenShift uses to automate AWS load balancer provisioning. As a result, automated creation and management of AWS Application Load Balancers (ALBs) might not be available. In these environments, you might need to manually configure ingress resources. To configure these resources, use predefined ingress manifests or alternative ingress architectures.
    Note If you use AWS Classic Load Balancers (CLBs), carefully review the connection and idle timeout limits. CLBs terminate long-lived idle connections, which can interrupt SystemLink client connectivity.
Note For region-specific service availability and endpoint details, refer to the public documentation.