Before You Start

Autonomous Identity server software requires the following hardware and software requirements to run in your production environment. Autonomous Identity's flexible architecture runs in a variety of network environments: on-prem, cloud, multi-cloud, and hybrid.

Files to Download

You deploy Autonomous Identity using a Docker image that pulls other dependent images from the ForgeRock Google Cloud Registry (gcr.io) repository and installs the components on a target node. ForgeRock Autonomous Identity customers must contact ForgeRock for a registry key to download the images. For specific instructions on obtaining the registry key, see How To Configure Service Credentials (Push Auth, Docker) in Backstage.

Autonomous Identity requires the following Docker image for installation.

Autonomous Identity Software
Docker ImageDocker Image URL

gcr.io/forgerock-autoid/deployer:2020.10.1

Download the image file from the ForgeRock Google Cloud Repository at https://gcr.io/forgerock-autoid/deployer:2020.10.1.


Hardware and Memory Requirements

Autonomous Identity has a number of components that include application, data, and analytics servers, which are all included in the Docker images. The minimum hardware and memory requirements for a single-node deployment are as follows:

Table 1: Hardware and Memory Requirements
VendorVersions
Application and Data Server32 GB RAM, 8 CPU
Analytics and Administration Server64 GB RAM, 16 CPU

Storage Requirements

Autonomous Identity has a number of components that include application, data, and analytics servers, which are all included in the Docker images. The minimum hardware and memory requirements for a single-node deployment are as follows:

Table 1: Hardware and Memory Requirements
VendorVersions
Application and Data Server32 GB RAM, 16 CPU
Analytics and Administration Server64 GB RAM, 16 CPU

Autonomous Identity requires the following minimum storage requirements:

Table 2: Storage Requirements
TypeSize
Data Storage1 TB

Operating Systems Requirements

Autonomous Identity is supported on the following operating system:

Table 3: Operating System Requirements
VendorVersions
CentOS7.7 and higher

Java Requirements

Autonomous Identity software supports the following Java environments:

Table 4: Java Requirements
VendorVersions
OpenJDK8u262 and higher

Third Party Software Requirements

Autonomous Identity deployments use the following third-party software:

Table 5: Third-Party Software Requirements
ComponentVersionUsage
Python3.6 and higherScripts
Docker CE18.09.1Container cluster management
Apache Cassandra3.11.2 and higherDatabase for all Autonomous Identity services
Apache Spark2.4.4 and higherCluster to run Autonomous Identity analytics
Mongo DB4.4Database for all Autonomous Identity services
HashiCorp Consul1.7 and higherService discovery and configuration server
nginx1.18 and higherReverse proxy for routing HTTPS traffic
Open Distro for Elasticsearch1.9 and higherDistributed, open source search engine for all data types.
OpenLDAP2.4.50 and higherAn LDAP server backend.

Supported Browsers

The following browser is supported for use in production:

Table 6: Supported Browsers
VendorVersions
Google Chromeversion 85.0.4183.121 and higher

Autonomous Identity Ports

The following ports are implemented in Autonomous Identity:

Table 7: Autonomous Identity Ports
PortProtocolMachineDescription
2376TCPDocker

Secure Docker client communication. This port is required for the Docker machine, which orchestrates the Docker hosts.

2377TCPDocker

Communication between the nodes of a Docker swarm cluster. Only needed on manager nodes.

7946TCP/UDPDocker

Communication among nodes for container network discovery.

4789UDPDockerOverlay network traffic.
7001TCPCassandraInternode communication.
9042TCPCassandraCQL native transport.
27017TCPMongoDBDefault ports for mongod and mongos instances.
5601TCPOpen Distro for ElasticsearchPort to access Kibana.
7077TCPSparkSpark master internode communication port.
40040-40045TCPAnalytics

Spark driver ports for Spark workers to callback.

443TCPAutonomous IdentityPort to access the dashboard and API.
5601TCPAutonomous IdentityPort to Kibana.

Read a different version of :