File Access Manager General Information

When installing File Access Manager, the following is some information that could help in understanding the product and the process of installing.

File Access Manager Architecture

File Access Manager architecture usually requires a central installation with some remote gateways. Most File Access Manager connectors do not require any footprint on the monitored/analyzed system and therefore are installed on File Access Manager servers.

In some cases, due to 3rd party vendors (mostly NAS vendors), it is imperative to have a local server at the same physical site where the monitored system is located.

For more information on File Access Manager architecture see “Capabilities and Architecture” in the File Access Manager Administrator Guide.

File Access Manager Connector Services

Each type of connector has its own prerequisites and its own configuration. See the relevant Connector Installation guide for more information about the connector.

Sizing Considerations

File Access Manager is a scalable solution that enables the distribution of its services and also works in an all-in-one mode. The Administrator Guide has a complete description of the File Access Manager architecture configuration.

One of the critical sizing considerations is the amount of disk space required to store activities over time. The table below describes the guidelines.

Note: For more details on sizing, refer to the File Access Manager Hardware Sizing Guide article on Compass.

Service	CPU	Memory	Disk
Elasticsearch	Minimum of 4 cores, Recommended 8	Minimum of 8Gb, Recommended 16Gb	0.5kb per event

Additional factors that affect the required hardware are:

• Disaster recovery environment

• High Availability solution

It is highly recommended to consult with your SailPoint File Access Manager representative to obtain the correct configuration to support your requirements.