1.10 Supported Appliance Components and Software
Key Takeaways
Cloud Connector Gateway is enabled by default on SailPoint Identity Security VA clusters.
For an eligible Standard cluster, select licensed components and check their egress support before enabling them.
Privileged Access Gateway supports standard or HTTP proxy egress. Data Access Security VA components require standard egress.
SailPoint documents restricted administration of the standard image and a separate limited-availability customer-provided operating system option.
Check four things before enabling a component
A virtual appliance component is a SailPoint capability configured on the cluster. Start with the business objective, then verify the organization’s license, the cluster type, the network mode and the resource requirements. A checkbox in the tenant is one part of the deployment. The host still has to provide the necessary compute and memory, and the appliance has to communicate over an egress configuration supported by that component.
Cloud Connector Gateway (CCG) is the default component for SailPoint Identity Security VA clusters. It is part of the supported VA connector design. SailPoint describes deselecting CCG for a dedicated appliance that is intended only to run one SailPoint product component. Confirm how sources depend on the cluster before altering that default. If the cluster runs connectors for a private directory, a plan to remove its connector component should include a separate supported path for the directory first.
| Proposal | What the engineer must establish |
|---|---|
| Add a licensed Privileged Access Gateway | Use a Standard cluster with a supported standard or HTTP proxy network configuration. A network tunnel is incompatible with this component. |
| Add Data Access Security VM components | Use a licensed configuration with standard direct egress. HTTP proxy and network tunnel configurations are incompatible. |
| Add components to an older Default cluster | The tenant manages component selection on the Standard cluster type. Older Default clusters do not support that edit. |
| Reuse a machine sized for a basic appliance | Compare its actual resources with revised component requirements. Size every member for the components it will run. |
| Install a general-purpose application on the standard VA image | Treat the appliance as a managed host with documented administrative boundaries. Use an independent supported host for unrelated applications. |
The Standard cluster type is a cluster setting. Standard egress describes how the appliance reaches required endpoints. An engineer can have a Standard cluster whose network configuration is an HTTP proxy. Read both properties from the case. Licenses, cluster type, and networking answer different compatibility questions.
Work through a licensed deployment
A customer with SailPoint Privilege wants privileged workflow actions on private systems. It uses a Standard cluster with HTTP proxy egress. The product is licensed, the gateway supports that network mode, and the team can add the required resources per appliance. It can evaluate enabling the Privileged Access Gateway for this use. The sizing requirements page lists a gateway addition of two processors and four gigabytes of memory per appliance. If a supported starting image needs four processors and sixteen gigabytes for the environment in the example, the combined minimum becomes six processors and twenty gigabytes per appliance. These figures add resources to the stated image baseline. An actual infrastructure plan must select a supported host size meeting its own platform-specific requirements.
That same customer wants to add Data Access Security’s Activity Monitor. This component requires standard egress, which the proxy-configured cluster does not provide. Plan a supported standard-egress deployment with the network team. Changing cluster memory or the product license alone cannot make HTTP proxy egress compatible with this component. Use a separate supported configuration if the existing cluster has to remain on the proxy.
Some connector dependencies are separate services even though the connector uses a VA. SailPoint’s IQService, for example, belongs on a supported Windows server with the necessary target connectivity. The VA-to-IQService connection requires Transport Layer Security (TLS). A Windows-dependent connector action can therefore require changes on the Windows host without justifying software installation on the Linux appliance.
Apply the right operating system rules
The standard image uses Flatcar and SailPoint documents limitations on adding users, direct access to the trust or key store, and root access. Supported settings such as VA observability and cluster components are configured by their documented methods. For an organization that must run approved ancillary host tools, SailPoint provides a limited-availability customer-provided operating system option for eligible customers. The official terms describe additional agreements, approved operating systems and dedicated appliances. The customer assumes responsibility for the operating system and the non-SailPoint tools it installs. The image option does not override the licensed component’s own deployment requirements.
See SailPoint’s cluster component compatibility, resource additions, standard image limitations customer-provided operating system prerequisites and IQService placement and TLS.
A licensed tenant uses a Standard cluster with HTTP proxy egress. Which planned component matches that egress mode, assuming the appliance is sized correctly?
Data Access Security Activity Monitor
Privileged Access Gateway
Data Access Security Resource Collector
Data Access Security Permission Collector
An approved base image needs four processors and sixteen gigabytes per appliance. If SailPoint’s gateway component adds two processors and four gigabytes, what minimum does each appliance need in this example?
Four processors and sixteen gigabytes
Six processors and sixteen gigabytes
Four processors and twenty gigabytes
Six processors and twenty gigabytes
Sections you finish are checked off in the contents.