Beginning with release 12.0, the SBC Core supports the Ribbon Application Management Platform (RAMP), which replaces the EMS.
However, the EMA, CLI and API will continue to include EMS-labeled parameters and screens to facilitate SBC migrations from older releases. Accordingly, any references to "EMS" in this documentation pertain to the RAMP platform.
In this section:
Prerequisites for AWS CFN Install of SBC HA Instance
Prior to initiating a CFN-based install of an HA SBC instance, perform the following:
- Create a VPC for use in the deployment. Refer to Create a VPC for the SBC SWe.
- Create Internet Gateway for use in the deployment. Refer to Create an Internet Gateway for SBC SWe
- Create Key Pairs for Linux shell access and Administrator access. Refer to Create Key Pairs for the SBC SWe.
- Create Subnets for use in the deployment. Refer to Create Subnets for the SBC SWe.
- Create Security Groups for use in the deployment. Refer to Create Security Groups for SBC SWe.
- Update or create Route tables for the newly created subnets. Refer to Create Route Tables for SBC SWe.
- Create a placement group for the SBC deployment. Refer to Create Placement Groups.
- Create a Policy and Role for the SBC instance. Refer to Create an Identity and Access Management (IAM) Role for SBC SWe.
Instantiate an HA SBC Instance
To instantiate a standalone instance:
Log onto the AWS.
Click the Services drop-down list.
The Services list is displayed.Click CloudFormation from Management Tools section.
The stacks page displays.
Click Create Stack. The Select Template page displays.
- In the Choose a template section, select Upload a template to Amazon S3.
- Click Choose File to navigate through the folders and select the template.
The selected template displays. Click Next.
The Create A New Stack page displays.NoteIf you wish to use pre-allocated EIPs for management, set EIPAssociationForMgt to No at that field prompt.
After the deployment has completed, you will need to manually associate the pre-allocated EIP to Mgmt (Eth0) Primary and secondary IPs.
NoteRibbon recommends using an RAMP Private IP in the CFN template for RAMP registration. If a public IP is used for RAMP registration using the SBC CFN template, then you must add the RAMP public IP to the SBC security group rules for communication.
In the Stack name field enter a unique name for this SBC stack. A stack is a collection of AWS resources you create and delete as a single unit.
Enter the required values for the Parameter fields. The following table describes the create stack parameters.
CautionThird party CPU setting of more than two vCPU is not supported with p3.2xlarge instances due to the vCPU requirement of the Standard_GPU_Profile.
- Click Next.
The Options page displays. Optionally you can choose to Tag your deployment with a Key-value pair, IAM Role Permissions, Rollback Triggers or other advanced Options.
- Click Next.
The Review page displays. - Review the stack details and click Create
The CloudFormation Stacks page displays.
On successful stack creation, the stack is listed.
Do not update or modify the stack after creation.
Do not change or remove resources after instance creation. For example, removing or attaching EIP, or changing the user data and so on.
Verify the Instance Creation
Perform the following steps to view the SBC SWe instances created:
Click the Services drop-down list.
The Services list is displayed.From the left pane click EC2.
The EC2 Dashboard page is displayed.
From the left pane under Instances click Instances. The instances table lists the new instance.
CautionIf deleting an instance from 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).