FreeSBC:Cloud:AWS Installation A - Revision history

Luc Morissette at 18:16, 24 July 2025

2025-07-24T18:16:26Z

← Older revision		Revision as of 14:16, 24 July 2025
Line 1:		Line 1:
	{{DISPLAYTITLE:ProSBC:Cloud:AWS Installation}}		{{DISPLAYTITLE:ProSBC:Cloud:AWS Installation}}


			= '''Please refer to this page instead:''' [https://docs.prosbc.com/initial-installation/1.-instructions-by-platform/cloud-installation/cloud-aws ProSBC AWS installation] =

			__________________________________________________________________________________________



	This page is intended to give assistance to people launching an instance of ''ProSBC'' using an Amazon Machine Image (AMI) on Amazon Web Service (AWS).		This page is intended to give assistance to people launching an instance of ''ProSBC'' using an Amazon Machine Image (AMI) on Amazon Web Service (AWS).

Luc Morissette: /* Web Portal Initial Configuration */

2022-04-11T13:02:03Z

Web Portal Initial Configuration

← Older revision		Revision as of 09:02, 11 April 2022
Line 251:		Line 251:
	== Web Portal Initial Configuration ==		== Web Portal Initial Configuration ==
	Click on the following link to pursue installation from the web portal:		Click on the following link to pursue installation from the web portal:
	[[TSBC-SW:WebPortal:Initial Configuration:ProSBC Initial Configuration]]		[[TSBC-SW:WebPortal:Initial Configuration\|ProSBC Initial Configuration]]

	== Troubleshooting ==		== Troubleshooting ==

Luc Morissette: TSBC -> ProSBC

2022-04-11T13:01:52Z

TSBC -> ProSBC

← Older revision		Revision as of 09:01, 11 April 2022
Line 251:		Line 251:
	== Web Portal Initial Configuration ==		== Web Portal Initial Configuration ==
	Click on the following link to pursue installation from the web portal:		Click on the following link to pursue installation from the web portal:
	[[TSBC-SW:WebPortal:Initial Configuration]]		[[TSBC-SW:WebPortal:Initial Configuration:ProSBC Initial Configuration]]

	== Troubleshooting ==		== Troubleshooting ==

Luc Morissette: Still found some "TSBC" - replaced with ProSBC

2022-04-11T13:00:51Z

Still found some "TSBC" - replaced with ProSBC

← Older revision		Revision as of 09:00, 11 April 2022
Line 237:		Line 237:
	aws ec2 modify-instance-attribute --instance-id i-0123456789abcdef1 --sriov-net-support simple		aws ec2 modify-instance-attribute --instance-id i-0123456789abcdef1 --sriov-net-support simple

	== Accessing the ~~TSBC-SW~~ ==		== Accessing the ProSBC ==
	=== Accessing the ~~TSBC-SW~~ web portal ===		=== Accessing the ProSBC web portal ===
	* Open a web browser to the management IP of the ~~TSBC~~, on port 12358. Example if your Instance public IP address is 35.183.126.193, the URL would be: <br/> http://35.183.126.193:12358		* 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: <br/> http://35.183.126.193:12358
	<br/>		<br/>
	:You should get to the ~~TSBC~~ Configuration Wizard <br/>		:You should get to the ProSBC Configuration Wizard <br/>
	:[[File:AWS_TSBC_WebPortal_Configuration_wizard.jpg\|700px]]		:[[File:AWS_TSBC_WebPortal_Configuration_wizard.jpg\|700px]]
	<br/>		<br/>

Serdar Civici: /* Enable SR-IOV enhanced networking */

2022-04-11T11:55:37Z

Enable SR-IOV enhanced networking

← Older revision		Revision as of 07:55, 11 April 2022
Line 191:		Line 191:
	It is very important to enable "enhanced networking" for tbrouter to have access to the network devices on the VM.		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.		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.		There are two types of enhanced networking, we need the second one.

Serdar Civici at 06:04, 21 February 2022

2022-02-21T06:04:07Z

← Older revision		Revision as of 02:04, 21 February 2022
Line 233:		Line 233:
	}		}

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

Luc Morissette: Minor

2021-04-06T12:18:56Z

Minor

← Older revision		Revision as of 08:18, 6 April 2021
Line 31:		Line 31:
	! width="150" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| EC2 Instance		! width="150" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| EC2 Instance
	! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| AWS CPU cores		! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| AWS CPU cores
	! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| Sessions/s		! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| Sessions per second (call rate)
	! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| Sessions with RTP anchoring		! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| Sessions with RTP anchoring
	! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| Sessions with Media bypass		! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| Sessions with Media bypass

Jean-Pierre Marcil: /* Accessing the TSBC-SW */

2021-03-31T17:21:08Z

Accessing the TSBC-SW

@@ Line 187: / Line 187: @@
 * Click on "Instances" on the left pane and select "ProSBC" instance. Check if your instance is associated with a public IP:
 [[File:Ready.png| 1100px]]
 == Accessing the TSBC-SW ==

Serdar Civici: /* Optional: Adding additional interface */

2021-01-11T14:52:37Z

Optional: Adding additional interface

← Older revision		Revision as of 10:52, 11 January 2021
Line 187:		Line 187:
	* Click on "Instances" on the left pane and select "ProSBC" instance. Check if your instance is associated with a public IP:		* Click on "Instances" on the left pane and select "ProSBC" instance. Check if your instance is associated with a public IP:
	[[File:Ready.png\| 1100px]]		[[File:Ready.png\| 1100px]]

	~~=== Optional: Adding additional interface ===~~
	~~Click on the following link to see how to add an additional interface to an existing instance~~
	* [[FreeSBC:Cloud:AWS_Additional_Interface_A\|Adding additional interface to AWS Instance]]

	== Accessing the TSBC-SW ==		== Accessing the TSBC-SW ==

Serdar Civici: /* Troubleshooting */

2020-12-17T09:59:03Z

Troubleshooting

← Older revision		Revision as of 05:59, 17 December 2020
Line 210:		Line 210:
	== Troubleshooting ==		== Troubleshooting ==
	* [[FreeSBC:Cloud:AWS_Installation_Troubleshooting_A\|Installation troubleshooting]]		* [[FreeSBC:Cloud:AWS_Installation_Troubleshooting_A\|Installation troubleshooting]]
			* [[FreeSBC:Cloud:Recovering_an_Elastic_IP_address\|Recovering an Elastic IP address]]
	[[Category:Revise on Major]]		[[Category:Revise on Major]]

	== External References ==		== External References ==
	* [https://devops.profitbricks.com/tutorials/use-ssh-keys-with-putty-on-windows/#connect-to-server-with-private-key Accessing device with SSH and private key using putty]		* [https://devops.profitbricks.com/tutorials/use-ssh-keys-with-putty-on-windows/#connect-to-server-with-private-key Accessing device with SSH and private key using putty]

← Older revision		Revision as of 08:18, 6 April 2021
Line 31:		Line 31:
	! width="150" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| EC2 Instance		! width="150" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| EC2 Instance
	! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| AWS CPU cores		! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| AWS CPU cores
	! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| Sessions/s		! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| Sessions per second (call rate)
	! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| Sessions with RTP anchoring		! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| Sessions with RTP anchoring
	! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| Sessions with Media bypass		! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| Sessions with Media bypass