The following is a general example for launching a new virtual instance. The exact process can vary depending on the customer network requirements.
Procedure
Sign in to your AWS account. Click Services and select EC2.
From the top-right corner, select the zone appropriate to the customer location.
Click Launch Instance and select Community AMIs and enter Avaya as the search string.
Locate the IP Office AMI and click Select.
The name of the file indicates the release of IP Office software.
The same image is used to create different types of IP Office server. The server type is selected during initial server configuration.
Select a machine instance that matches the profiling requirements of the virtual machine's intended role. See AWS profiling.
Click Next.
In Configure Instance Details page, select the customer's VPC and the subnet in which the virtual machine should operate.
To support eth1, under Network interfaces, click Add Device.
If you use this option, AWS will not automatically assign IP addresses to the ports. After launching the instance, you must obtain the eth0 interface ID and assign a Elastic IP public IP address.
Click Next.
In Add Storage page, set the size of the disk to match the profiling requirements of the virtual machine's intended role. See AWS profiling.
Note: Adjusting the disk size following server ignition is not supported.
To achieve the stated capacity and performance, you must provision all IP Office virtual disks as Thick Provision Eager Zeroed or the equivalent for the particular hosting platform.
If the server will support Media Manager, you must add an additional separate storage volume. To add this, click Add New Volume and specify the size required.
Click Next.
In Add Tags page, enter any tags that you want associated with this instance.
AWS uses tags in other EC2 menus to display, sort and group matching resources. Each tag consists of name and value pair. For example, you may find it useful to have tags that indicate the server type, the location it serves and the customer
Click Next.
In Configure Security Group page, select the system installer's security group you created. See Creating security groups.
Important:
When launching a new instance, you should use a highly restricted security group that allows access from as few hosts and protocols as possible. For example, one that allows access from your IP address and using HTTPS access to ports 7070/7071 only. This is necessary since the new instance boots with default passwords until initial configuration is completed. Following server ignition, you can assign a different security group that allows the access required for normal IP Office operation.
If you do not select a group, the install process automatically creates a launch wizard group which allows SSH access on port 22 only.
Click Review and Launch. Check that the details shown match the requirements for the server being created. If so, click Launch.
Create a new key pair or choose an existing key pair. This provides a security certificate for secure SSH access to the virtual machine.
If creating a new key pair, click Download Key Pair and ensure that you store the downloaded PEM certificate file in a safe place.
Click Launch Instances.
If no problems are reported, scroll down the summary form and click View Instances. The list of your instances displays the new virtual machine.
Alternatively, select Services > EC2 and from the navigation tree select Instances > Instances.
The machine starts by performing initial formatting and partitioning of the storage. This takes approximately 15 minutes to complete.
