Skip to content

(Deprecated) On-Prem Connector

Dependencies:

Minimum requirements

  • The instance should have egress communication and be able to access the internet

    • AWS Cloud (SailPoint Entro Servers)

    • ghcr.io (GitHub registry domain)

    • The instance should have access to your target on-prem servers (to allow the SailPoint Entro connector to communicate and scan your services).

    Optional: If you require passing through an HTTP proxy to access the internet from the instance, please let us know.

    SailPoint Entro remote connector onboarding options:

    • EKS / K8S

      • This is the preferable and easy-to-manage option.

      • We will use helm commands to install our helm chart.

      • Volume of at least 10 GIB storage.

      • Default limits spec per pod:

        • CPU: 2 CPU

        • Memory: 4Gi

      • One installation contains minimum 3 pods.

    • ECS

      • This is the right choice if you will be moving away from K8S (EKS) in the next 3 months.

      • We will provide the exact instructions based on your answer.

      • We have a script or a CloudFormation template to install the ECS cluster.

    • VM or Bare Metal

      • This is a good option if it is a temporary solution until you decide.

      • Must have a Linux VM with Docker installed that can communicate and have network access to your instances (Bitbucket, Jira, Confluence).

      • VM should have at least 8 CPU, 32 GIB memory, and 64 GIB of storage.