In this section:
AWS provides High Availability through the use of Elastic IP (EIP). With EIP, when a switchover from an active SBC instance to a standby instance is required, the IP address for the active server moves to the standby instance through a REST API call, which can result in a 15-20 second switchover time. While this solution may be acceptable for the majority of web-based applications, it does not meet the requirements needed for SBCs for real-time communications.
To accomplish switchover times closer to 2 seconds, an HA Front-End (HFE) was added to the AWS architecture solution to host the Elastic IP.
In this procedure, the private subnet for HFE is created automatically.
Info |
---|
|
The SBC SWe does not support IPSec in AWS. The High-Availability Front End (HFE) front-ends only one pkt port (pkt0), public endpoints can be connected only to pkt0. Pkt1 can serve private endpoints. |
Info |
---|
|
The HFE is configured using a script named "HFE.sh". This script is available in addition to example CloudFormation templates which support the deployment of an HA SBC with HFE. Both files are required to deploy an SBC with High-Availability Front-End. |
Info |
---|
|
If you delete an instance from the CFN, be aware that AWS does not delete volume(s) automatically. They must also be deleted from the AWS UI if you do not want volumes of deleted instances (standalone, HA or HFE-based SBC installation). |
Prerequisites for AWS CFN Install of HFE and SBC HA Instance with Automated HFE Private Subnet Creation
Prior to initiating a CFN-based install of an HA SBC instance with HFE perform the following:
- Download the CFN supporting HFE and the HFE configuration script (HFE.sh) to your desktop.
- Create a VPC for use in the deployment. Refer to Creating VPC for SBC.
- Create Internet Gateway for use in the deployment. Refer to Creating Internet Gateway for SBC.
- Create Key Pairs for Linux shell access and Administrator access. Refer to Creating Key Pairs for SBC.
- Create Subnets for use in the deployment - HFE Public, SBC Management, SBC HA0, SBC PKT0, SBC PKT1. Refer to Creating Subnets for SBC.
- Ensure space in VPC exists and determine subnet CIDR to use to create a new HFE Subnet (which is done by this CFN).
- Create Security Groups for use in the deployment. Refer to Creating Security Groups for SBC.
- Update or create Route tables for the newly created subnets. Refer to Creating Route Tables for SBC.
- Create a placement group for the SBC deployment. Refer to Creating Placement Groups.
- Create a Policy and Role for the SBC instance. Refer to Creating Identity and Access Management (IAM) Role for SBC.
- Create and Upload the HFE.sh script to S3 bucket. Refer to Upload HFE.sh script to S3.
- Create a Policy and Role for the HFE instance. Refer to Creating Identity and Access Management (IAM) Role for HFE.
- Locate the AMI ID in your region for an Amazon Linux 2 image. Refer to Finding Amazon Linux 2 AMI ID for use in HFE deployments.
Anchor |
---|
| InstantiateSA |
---|
| InstantiateSA |
---|
|
Instantiating an HFE and HA SBC Instance