# Cloud - AWS

### Introduction

This article provides guidance for people launching an instance of *ProSBC* using an Amazon Machine Image (AMI) on Amazon Web Service (AWS).\
NOTE The old installation guide is located here: [AWS installation](/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws/aws-installation.md)

### Instantiate a ProSBC

* After logging in your Amazon account, click on “EC2” in the main AWS console:

<figure><img src="/files/j9NsATiyXUwVX0e984SI" alt=""><figcaption></figcaption></figure>

* Be sure that you are in the correct region. Consult TelcoBridges if you are unsure which region to locate the AMI. On the left menu click on “AMIs” and select “Private image” to locate FreeSBC/ProSBC AMI:

<figure><img src="/files/r2VqIu86aGIvXH2NApAq" alt=""><figcaption></figcaption></figure>

* Launch the FreeSBC/ProSBC image.

<figure><img src="/files/ooAyoqW1Pt4A8LFhcksx" alt=""><figcaption></figcaption></figure>

* Name the instance and add any necessary tag

<figure><img src="/files/IBtBSKMaYrVZRwGcLQL7" alt=""><figcaption></figcaption></figure>

* Select the instance type and its resources. The smallest instance type is:

  * m5.large (2 vCPU, 8 GiB)

  The recommended instance type is:

  * m5.xlarge (4 vCPU, 16 GiB)
* Other supported instance type are:
  * C3, D2, I2, and R3 instances ([Supported instances from Amazon documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html))
* This is the list of approximate performances for different AWS instance types. Results may vary according to configuration.

<table><thead><tr><th width="150">EC2 Instance</th><th width="100">AWS CPU cores</th><th width="100">Calls per second (cps)</th><th width="100">Sessions with RTP anchoring</th><th width="200">Sessions with Media bypass</th></tr></thead><tbody><tr><td>m5.large</td><td>2</td><td>50</td><td>400</td><td>32,000</td></tr><tr><td>m5.xlarge</td><td>4</td><td>215</td><td>750</td><td>60,000</td></tr><tr><td>c5.2xlarge</td><td>8</td><td>575</td><td>2,000</td><td>60,000</td></tr><tr><td>m5.4xlarge</td><td>16</td><td>650</td><td>4,000</td><td>60,000</td></tr><tr><td>m5.12xlarge</td><td>48</td><td>650</td><td>4,800</td><td>60,000</td></tr></tbody></table>

<figure><img src="/files/DvTO2bq61Y93mJzymFfn" alt=""><figcaption></figcaption></figure>

* For later access to the FreeSBC/ProSBC SSH console you will need to select a Key Pair to secure the login. You can also create a new Key Pair in case you need.

<figure><img src="/files/5OrU8GIVd6Or9MbRip6N" alt=""><figcaption></figcaption></figure>

* In "Networking Settings" select "Create security group". We recommend that you simply open "All Traffic" on your own IP addresses to whitelist it in AWS firewall on "Source", once all your IPs are listed click on "Add security group rule": (note that the SBC contains its own internal firewall)

<figure><img src="/files/JzPdpf8mAgno83qFk09r" alt=""><figcaption></figcaption></figure>

* In "Configure Storage" change the Volume Size to 40Gb and select volume type to GP2.

<figure><img src="/files/7adtzT2Qn7ZUsXCaszGh" alt=""><figcaption></figcaption></figure>

* Finally review the summary of your instance and start the creation process clicking on "Launch Instance". Be aware, from this moment you will be billed by Amazon for the instance resources:

<figure><img src="/files/6peyH4A1Ld7Fe6NhNO71" alt=""><figcaption></figcaption></figure>

* You should receive the confirmation of the launching process, this process will take some minutes until the instance is available, You can view your instance clicking on “View Instances”:

<figure><img src="/files/LAbcRqUXKf9VWB4ZmeE3" alt=""><figcaption></figcaption></figure>

* After a few minutes your instance should be running and available to be configured:

<figure><img src="/files/GhhWxLoOFiVlv2hShcct" alt=""><figcaption></figcaption></figure>

<br>

#### Optional: Elastic IP Creation section

* AWS will automatically provide and allocate a dynamic public IP to your instance, this will allow you to access from the IPs you whitelisted before to the Public IP allocated to your instance. For ProSBC servers the purpose is to interact with other SIP elements as part of a VoIP cloud telecom infrastructure, TelcoBridges strongly recommends associating an Elastic IP to your instance, which is, in short, to associate a fixed public IP to your SBC. For more information about how to associate an Elastic IP to your instance please check the official documentation in AWS [here](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html).

### Enable SR-IOV enhanced networking

By default M5 instances have enhanced networking enabled. If you want to use any other instance, you need to check if enhanced networking is enabled or not.

```
It is very important to enable "enhanced networking" for tbrouter to have access to the network devices on the VM.
```

This must be done before completing the initial web portal configuration. Please shut down the instance before entering the serial number and all other information and set SR-IOV

There are two types of enhanced networking, we need the second one.

1\) Elastic Network Adapter (ENA)

2\) Intel 82599 Virtual Function (VF) interface

#### Install the AWS CLI

<https://aws.amazon.com/cli/>

#### Get security credentials for the command line

On the AWS web portal, click on your account name and choose "My Security Credentials"

Expand the "Access keys" section

Create a new key, you will need the AWSAccessKeyId and AWSSecretKey

#### Open a CLI and execute the aws cli commands

```
 aws configure
```

Paste the access key ID and key that you previously obtained along with your default region.

#### Show if the enhanced networking is enabled

Make sure to replace the example instance ID with your own AWS instance ID

```
 aws ec2 describe-instance-attribute --instance-id i-0123456789abcdef1 --attribute sriovNetSupport
```

Enabled:

```
 {
     "InstanceId": "i-0123456789abcdef1",
     "SriovNetSupport": {
         "Value": "simple"
     }
 }
```

Not enabled:

```
 {
     "InstanceId": "i-0123456789abcdef1",
     "SriovNetSupport": {}
 }
```

To enable the sriov enhanced networking, first turn off the instance then do:

```
 aws ec2 modify-instance-attribute --instance-id i-0123456789abcdef1  --sriov-net-support simple
```

### Accessing the ProSBC

#### Accessing the ProSBC web portal

* Open a web browser to the management IP of the ProSBC, on port 12358. Example if your Instance public IP address is 35.183.126.193, the URL would be:\
  [http://35.183.126.193:12358](http://35.183.126.193:12358/)

<br>

You should get to the ProSBC Configuration Wizard\
![](https://docs.telcobridges.com/w/images/thumb/0/01/AWS_TSBC_WebPortal_Configuration_wizard.jpg/700px-AWS_TSBC_WebPortal_Configuration_wizard.jpg)

<br>

Take note that it may take a while for the ProSBC system to make the Web Portal available (around 3-5 minutes).

* From here, you can go to [Web Portal Initial Configuration Guide](/initial-installation/2.-initial-configuration/initial-setup.md) to continue the installation.

### Installing AWS Instance with CloudFormation Template

AWS CloudFormation is a service that helps you model and set up your AWS resources so that you can spend less time managing those resources and more time focusing on your applications that run in AWS. Telcobridge created a CloudFormation template to reduce the time spent on ProSBC AWS installation. Click on the following link to the ProSBC CloudFormation installation: [ProSBCAWS CloudFormation Installation](/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws/cloud-formation-installation.md)

### Upgrading the instance type

You can upgrade the instance type in AWS based on your requirements. Click on the following link for instance type upgrade [ProSBC AWS Intance Upgrade](/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws/instance-upgrade.md)

### Adding more interfaces to ProSBC in AWS

You can add more interfaces to ProSBC in AWS based on your requirements. Click on the following link for how to add an interface [ProSBC AWS Additional Interface](/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws/aws-additional-interface.md)

### Web Portal Initial Configuration

Click on the following link to pursue installation from the web portal: [ProSBC Initial Configuration](/initial-installation/2.-initial-configuration.md)

### AWS using NAT

Since the AWS instance is behind NAT, you must adjust the NAT settings for the SBC: [IP Network Settings](/configuration-details/configuration-by-web-portal-category/ip-network-settings.md)

### Troubleshooting

* [Installation troubleshooting](/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws/aws-installation-troubleshooting.md)
* [Recovering an Elastic IP address](/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws/recovering-an-elastic-ip-address.md)

### External References

* [Accessing device with SSH and private key using putty](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect-to-linux-instance.html)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://prosbcdocs.telcobridges.com/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.