EC2 Deployment Procedure
Deploying the OCSBC on EC2 includes the following high-level steps:
1.
Launch your Instances on AWS—This is the main instance configuration
procedure. It includes a multi-dialog wizard that presents configuration options in
the preferred sequence. The result of this wizard is an installed, operational
OCSBC or two HA OCSBC instances with no networking.
2.
Configure the Network Interfaces for Your Instances—This is a preparatory task,
creating interfaces that you attach to instances in the next procedure.
3.
Attach the Network Interfaces to Your Instances—This assigns interfaces to
instances. Check your interface assignments using the OCSBC ACLI interface-
mapping commands, shown below, after OCSBC startup and correct interface
assignment, if necessary. See the Oracle® Communications Session Border
Controller Platform Preparation and Installation Guide for further instructions on
using these commands.
4.
Apply your OCSBC Configuration—This is an OCSBC ACLI configuration
procedure.
5.
During ACLI configuration, configure the first private address provided by EC2 for
media interfaces as the pri-utility-address, and the secondary private address as
the interface's ip-address when you configure your primary HA OCSBC.
6.
During ACLI configuration, you only need the first private address provided by EC2
for the secondary HA OCSBC media interface addresses. Configure that address
as each applicable media interface's sec-utility-address.
Deploying the OCSBC for HA, adds the following high-level considerations:
•
Configure an Identity and Access Management (IAM) Role for the OCSBCs—This
is a preparatory task.
•
Place both OCSBCs in the same Availability Zone.
•
A Place Group, of the type Spread, must be available, within which you place
both OCSBCs.
•
You must assign a public IP to the wancom0 management interface.
•
Configure Secondary Private IPs (Virtual IPs) for all Media Interfaces to create
virtual IPs for use during HA switchovers.
•
You must map the Secondary addresses used for Virtual IPs to Elastic IP
addressing.
•
The wancom0 management subnets must be public to allow access from outside
the cloud. You can meet this requirement by allowing an auto-assigned Public IP
or by configuring it with an Elastic IP.
For both HA and standalone deployments, all Media interfaces addresses that must be
reachable through the internet must reside on public subnets; all others can reside on
private subnets. In addition, you can create additional IP addresses for an interface,
allowing for different addresses on steering-pools, HIP, and other objects.
Your EC2 workspace may present dialogs and fields that differ from this procedure.
For full information on deploying EC2 instances, see the Amazon EC2 documentation.
Chapter 7
Create and Deploy OCSBC Instances on EC2
7-10
