Managing AWS instances
This section describes the common maintenance tasks for stopping, restarting and permanently removing Conferencing Node AWS instances, and how to add ENA support to an instance.
Temporarily removing (stopping) a Conferencing Node instance
At any time you can temporarily remove a Conferencing Node instance from your Pexip Infinity platform if, for example, you do not need all of your current conferencing capacity.
To temporarily remove a Conferencing Node instance:
-
Put the Conferencing Node into maintenance mode via the Pexip Infinity Administrator interface on the Management Node:
- Go to .
- Select the Conferencing Node(s).
-
From the Action menu at the top left of the screen, select Enable maintenance mode and then select .
While maintenance mode is enabled, this Conferencing Node will not accept any new conference instances.
- Wait until any existing conferences on that Conferencing Node have finished. To check, go to .
-
Stop the Conferencing Node instance on AWS:
- From the AWS management console, select to see the status of all of your instances.
- Select the instance you want to shut down.
- From the Actions drop-down, select to shut down the instance.
Reinstating (restarting) a stopped Conferencing Node instance
You can reinstate a Conferencing Node instance that has already been installed but has been temporarily shut down.
To restart a Conferencing Node instance:
-
Restart the Conferencing Node instance on AWS:
- From the AWS management console, select to see the status of all of your instances.
- Select the instance you want to restart.
- From the Actions drop-down, select to start the instance.
-
Take the Conferencing Node out of maintenance mode via the Pexip Infinity Administrator interface on the Management Node:
- Go to .
- Select the Conferencing Node.
- Clear the Enable maintenance mode check box and select .
-
Update the Conferencing Node's static NAT address, if appropriate.
If your Conferencing Node instance was configured with an auto-assigned public IP address, it will be assigned a new public IP address when the instance is restarted.
- Go to Conferencing Node. and select the
- Configure the Static NAT address as the instance's new public IP address.
After reinstating a Conferencing Node, it takes approximately 5 minutes for the node to reboot and be available for conference hosting, and for its last contacted status to be updated on the Management Node.
Permanently removing a Conferencing Node instance
If you no longer need a Conferencing Node instance, you can permanently delete it from your Pexip Infinity platform.
To remove a Conferencing Node instance:
- If you have not already done so, put the Conferencing Node into maintenance mode via the Pexip Infinity Administrator interface on the Management Node:
- Go to .
- Select the Conferencing Node(s).
From the Action menu at the top left of the screen, select Enable maintenance mode and then select .
While maintenance mode is enabled, this Conferencing Node will not accept any new conference instances.
- Wait until any existing conferences on that Conferencing Node have finished. To check, go to .
-
Delete the Conferencing Node from the Management Node:
- Go to Conferencing Node. and select the
- Select the check box next to the node you want to delete, and then from the Delete selected Conferencing Nodes and then select . drop-down menu, select
-
Terminate the Conferencing Node instance on AWS:
- From the Amazon VPC console, select to see the status of all of your instances.
- Select the instance you want to permanently remove.
- From the Actions drop-down, select to remove the instance.
Adding ENA support to an instance
As of version 21, Pexip Infinity supports AWS instance types that use the Elastic Network Adapter (ENA). This includes C5 instance types.
If you are switching to a C5 instance and your node was originally deployed with version 20 or earlier, then you need to add ENA support to the instance, otherwise your instance will not start:
- Ensure that your Pexip Infinity platform is running version 21 or later.
- Shut down the instance.
-
Run the AWS CLI command:
aws ec2 modify-instance-attribute --instance-id <instance_id> --ena-support
See this article for the PowerShell variant.
-
Run the following command to confirm ENA support has been added:
aws ec2 describe-instances --instance-ids <instance_id> --query "Reservations[].Instances[].EnaSupport"
It should output:
[ true ]
- Power on the instance type (or change the instance type and power on).