In this section:
Prior to initiating a CFN-based install of an HA SBC instance, perform the following:
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.
Click Next.
The Create A New Stack page displays.
If 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.
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.
Third 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.
Create Stack Parameters
Parameter Section | Field | Description | Mandatory | Can Leave Blank | Customizable by User |
---|---|---|---|---|---|
Elastic IP configuration | EipAssociationOnMgt | Select Yes from the drop-down to associate EIP for MGT0 interface to login and access SBC application from public networks. Select No if EIP is not required. | |||
Elastic IP configuration | NumberOfEIPOnPkt0 | The number of Elastic IPs to be associated with PKT 0 interface. Note: Default is 0 | |||
Elastic IP configuration | NumberOfEIPOnPkt1 | The number of Elastic IPs to be associated with PKT 1 interface. Note: Default is 0 | |||
Network configuration | SecurityGrpHa0 | Acts as a firewall for associated Amazon EC2 instances, controlling both inbound and outbound traffic for HA0. | |||
Network configuration | SecurityGrpMgt0 | Acts as a firewall for associated Amazon EC2 instances, controlling both inbound and outbound traffic for MGT0. | |||
Network configuration | SecurityGrpPkt0 | Acts as a firewall for associated Amazon EC2 instances, controlling both inbound and outbound traffic for PKT0. | |||
Network configuration | SecurityGrpPkt1 | Acts as a firewall for associated Amazon EC2 instances, controlling both inbound and outbound traffic for PKT1. | |||
Network configuration | SubnetIdHA0 | Subnet ID of an existing subnet in your Virtual Private Cloud (VPC) for HA0. | |||
Network configuration | SubnetIdMgt0 | Subnet ID of an existing subnet in your Virtual Private Cloud (VPC) for Mgt0. | |||
Network configuration | SubnetIdPkt0 | SubnetId of an existing subnet in your Virtual Private Cloud (VPC) for Pkt0. | |||
Network configuration | SubnetIdPkt1 | SubnetId of an existing subnet in your Virtual Private Cloud (VPC) for Pkt1. | |||
Network configuration | VpcId | Select a VPC with Subnet, Security Group, etc., selected earlier. | |||
Placement of Instance | PlacementId | A placement group ID of logical group of instances within a single Availability Zone. This is an optional field and can be blank. | |||
Placement of Instance | Tenancy | The Tenancy Attribute for this instance. | |||
Reverse NAT configuration | ReveseNatEnablePkt0 | Enable or disable reverse Network Address Translation (NAT) functionality for PKT0 interface. Set this field to true, to attach the assigned EIP on PKT0 and use it without SMM rule. Refer to EipAssociationXface for associating EIP for the required interfaces. Note: When set to False, the SBC application cannot use the attached EIP. | |||
Reverse NAT configuration | ReveseNatEnablePkt1 | Enable or disable reverse Network Address Translation (NAT) functionality for PKT1 interface. Set this field to true, to attach the assigned EIP on PKT1 and use it without SMM rule. Refer to EipAssociationXface for associating EIP for the required interfaces. Note: When set to False, the SBC application cannot use the attached EIP. | |||
Secondary IP configuration for PKT0 and PKT1 | NumberOfAlternateIPOnPkt0 | Alternate IP address for packet port 0. Note: Default is 1. If you are using more than one IP for alternate IPs, use comma separated IPs list. | |||
Secondary IP configuration for PKT0 and PKT1 | NumberOfAlternateIPOnPkt1 | Alternate IP address for packet port 1. Note: Default is 1. If you are using more than one IP for alternate IPs, use comma separated IPs list. | |||
Security configuration | AdminSshKey | Existing EC2 KeyPair name to enable SSH access to admin CLI on SBC instance. | |||
Security configuration | LinuxAdminSshKey | Existing EC2 KeyPair name to enable SSH access to Linux shell on SBC instance. | |||
Storage configuration | IOPS | Enter IOPS reservation for io 1 type EBS volume | |||
Storage configuration | VolumeSize | Enter the size of disk required in GB. The minimum size is 65 GIB. However, you can choose more. | |||
Storage configuration | VolumeType | Select the type of volume for SBC. Ribbon recommends that SBC use io1 type. | |||
System configuration | ActiveInstanceName | This specifies the actual CE name of the SBC active instance. For more information, refer to System and Instance Naming in SBC SWe N:1 and Cloud-Based Systems. CEName Requirements:
| |||
System configuration | AMIID | Amazon Machine Image (AMI) is an encrypted machine image which is like a template of a computer's root drive. For example, ami- xxxxxxxx . | |||
System configuration | IAMRole | The name of the IAM role for SBC SWe instance. For more information on IAM Role, refer to Creating Identity and Access Management (IAM) Roles. | |||
System Configuration | EnableCloudWatchMetrics | Enable this for capturing instance metrics at cloudwatch. Note: Default is false. | Yes , when CloudWatch features are using Interval Stats | ||
System configuration | InstanceType | Type of instance created from stack. Note: Ribbon recommends m5.xlarge or higher instance type if this instance type is available in your zone. Use c5.2xlarge instance type or higher to handle more calls with transcoding. | |||
System configuration | SBCPersonality | The type of SBC for this deployment. In this release, always set the personality to isbc. | |||
System configuration | StandbyInstanceName | This specifies the actual CE name of the SBC standby instance. For more information, refer to System and Instance Naming in SBC SWe N:1 and Cloud-Based Systems. CEName Requirements:
| |||
System configuration | SystemName | Specifies the actual system name of the SBC instance. For more information, refer to System and Instance Naming in SBC SWe N:1 and Cloud-Based Systems. System Requirements:
| |||
System Configuration | UseAnonymizationFeature | Enable this for Anonymization. Note: Default is false. | Yes, when CloudWatch features are using ACT, TRC | ||
Third Party Applications Provisioning | ThirdPartyCPUs | Enter the number of CPUs to be reserved for use with third-party apps. Note: Default is 0 | Yes, when using CloudWatch features | ||
Third Party Applications Provisioning | ThirdPartyMem | Enter the number of MB of memory to be reserved for use with third-party apps. Note: Default is 0 | Yes, when using CloudWatch features |
Optionally you can choose to Tag your deployment with a Key-value pair, IAM Role Permissions, Rollback Triggers or other advanced Options.
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.
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.
If 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).