FreeSBC:Cloud:AWS Installation A

From TBwiki
(Difference between revisions)
Jump to: navigation, search
(update aws installation part 2)
(update aws installation part 3)
Line 41: Line 41:
 
[[File:NextSecurityGroup.png| 800px]]
 
[[File:NextSecurityGroup.png| 800px]]
  
* Select "Create a new security group" ( you can change its name and description). Then, click "Add Rule" to add a new rule as follow:
+
* Select "Create a new security group". You need at least 4 rules (Important: Adjust the source IPs to known IP addresses only):
** Type: Custom TCP Rule
+
** Protocol: TCP
+
** Port Range: 12358
+
** Source: My IP (will make this instance only accessible from your current computer IP)
+
  
 +
{| class="wikitable"
 +
|-
 +
! Rule !! Type !! Port Range
 +
|-
 +
| SSH || TCP || 22
 +
|-
 +
| Web Portal || TCP || 12358
 +
|-
 +
| SIP || UDP || 5060
 +
|-
 +
| RTP || UDP || 20000-40000
 +
|}
 
[[File:AddRule.png| 1000px]]
 
[[File:AddRule.png| 1000px]]
  

Revision as of 14:50, 9 March 2018


This page is intended to give assistance to people launching an instance of FreeSBC using Amazon Machine Image (AMI) on Amazon Web Service (AWS). In the Troubleshot section, instructions are suggested for a potential issue that a user may encounter.

Contents

Instantiate a FreeSBC

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

ConsoleEC2.png


  • On the left menu, click on “AMIs”:

AMIs.png


  • Click on the filter drop list and select “Private image” to locate FreeSBC AMI:

PrivateImages.png


  • Select the image and click “Launch”: (Check the troubleshooting section if you have a launching issues)

SelectAMI.png


  • Select the instance type and its resources. Supported instance type:
    • m4.large (2 vCPU, 8 GiB)

SelectResources.png


  • Choose an existing subnet from the list (Do not leave it to default):
  • Click "Add Device" under Network Interface section (as FreeSBC requires 2 network interfaces)
  • Click “Add Storage”:

ChooseSubnet.png


  • Change the Volume Size to 40Gb.
  • Select "Volume Type": gp2
  • Click “Add Tags”:

NextTag.png


  • You can leave the default parameters as they are.
  • Click “Configure Security Group”:

NextSecurityGroup.png

  • Select "Create a new security group". You need at least 4 rules (Important: Adjust the source IPs to known IP addresses only):
Rule Type Port Range
SSH TCP 22
Web Portal TCP 12358
SIP UDP 5060
RTP UDP 20000-40000

AddRule.png


  • Click “Review and Launch”:

ReviewLaunch.png


  1. Click “Launch”. Please, note that FreeSBC is free of charges. However, you will still be charged by Amazon for using their resources that you allocated:

Launch.png


  1. You will be prompted to create a key pair, allowing you to securely connect to your instance. Select “Create a new key pair” if you do not own one, and give it a name. Then, click on “Download Key Pair” to download a .pem file since it is needed for a secured SSH connection:

DownloadKey.png


  1. Click on “Launch Instances”:

LaunchWithKey.png


  1. You can view your instance by clicking on “View Instances”:

ViewInstance.png


  1. Select the instance you just created, and give a name:

RenameInstance.png


  1. For your instance to become accessible, you need to associate a public IP generated by Amazon. Click on "Elastic IP" on the left, then click on "Allocate new address":

ElasticIP.png


  • Click on "Allocate IP". A new public IP will be generated by Amazon: AllocateIP.png
  • Click on "Close": NewIP.png
  • Go to the left pane and click on "Instance". Then select the instance "FreeSBC" to display its description: IPforInstance.png
  • Notice the main Private IP circled in green. You need to identify which of the network interfaces is associated with it. Usually, it is the first in the list: GetTheRightNetworkInterface.png
  • Click on the identified Network Interface associated with the main Private IP, then click on "Interface ID" link: InterfaceID.png
  • Right-click on the selected Network Interface, then click "Associate Address": AssociateAddress.png
  • In the Address list, select the public IP to associate with the main Network Interface. Then, click on "Associate Address": SelectAddress.png
  • Click on "Instances" on the left pane and select "FreeSBC" instance. Check if your instance is associated with a public IP: Ready.png

    You are ready to connect to FreeSBC instance on AWS through the Web Portal.


    Troubleshooting

    If you come across the following issue, please follow the suggested instructions:

    Launch Failed after step 4

    FailedLaunch.png

       Follow the link:
    

    FailedLaunchLink.png


  • Click on “Continue to Subscribe”: Subscribe.png
  • If you agree with Amazon conditions, click on “Accept Software Terms & Launch with 1-click”. Now, you are ready to launch the instance you need: Accept.png

    Test if FreeSBC is up and running in real-time

    You can open a session of the image running CentOS7 and check the status of FreeSBC in real-time. Depending on your operating system, you can follow the links on Amazon guide to do so:

    Your Computer Topic
    Linux Connecting to Your Linux Instance Using SSH
    Windows Connecting to Your Linux Instance from Windows Using PuTTY
    All (using Firefox, Edge or Internet Explorer) Connecting to Your Linux Instance Using MindTerm
  • Personal tools