As the number of users and demands for web resources increase, you can easily add another Identity Server or Access Gateway to handle the load. The cluster configuration is sent to the newly added components automatically.
Scaling up a node when the Access Manager component is not deployed in the cloud virtual machine
Perform the following steps to scale up a node:
Create new virtual machines. For AWS EC2, see Creating and Deploying Instances and for Azure, see Creating and Deploying Virtual Machines.
Install the required Access Manager component and import that component to Administration Console.
After importing the component, log in to Administration Console and assign the imported component to the required cluster.
Access the cloud console (Azure or AWS EC2) and add the newly imported component to the load balancer group or target group.
Scaling up a node when the Access Manager component is installed in the cloud virtual machines, but not imported into the cluster
Perform the following steps to scale up a node:
Switch on the cloud virtual machine on which the required component is installed.
Access the terminal of the server and initiate the ag_import or idp_import script depending on the type of server.
Specify the Administration Console IP address while importing the component.
After importing, log in to Administration Console and assign the imported component to the required cluster.
Access the cloud console (Azure or AWS EC2) and add the newly imported component to the load balancer group or target group.