FreeSBC:Cloud:AWS Installation A

From TBwiki
Revision as of 09:35, 28 February 2018 by Mohamad Badreddine (Talk | contribs)
Jump to: navigation, search

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

Procedure to instanciate an AMI

  1. After logging in your Amazon account, click on “EC2” in the main AWS console:
  2. ConsoleEC2.png


  3. On the left menu, click on “AMIs”:
  4. AMIs.png


  5. Click on the filter drop list and select “Private image” to locate FreeSBC AMI:
  6. PrivateImages.png


  7. Select the image and click “Launch”: (Check the troubleshooting section if you have a launching issue)
  8. SelectAMI.png


  9. Select the instance type and its resources. For FreeSBC to run, you need to launch at least m4.large (2 vCPU, 8 GiB):
  10. SelectResources.png


  11. Click “Configure instance Details”:
  12. ConfigureDetails.png


  13. Choose an existing subnet from the default list (or create a new one if you want to change the default parameters):
  14. ChooseSubnet.png


  15. Click "Add Device" under Network Interface section (since FreeSBC needs two Network Interfaces). Leave the default parameters as they are:
  16. AddNewNetworkInterface.png


  17. Click “Add Storage”:
  18. NextStorage.png


  19. Change the volume Size to 40GiB. Then, click “Add Tags”:
  20. NextTag.png


  21. You can leave the default parameters as they are. Then, click “Configure Security Group”:
  22. NextSecurityGroup.png


  23. Select "Create a new security group" ( you can change its name and description). Then, click "Add Rule" to add a new rule as follow:
    • Type: Custom TCP Rule
    • Protocol: TCP
    • Port Range: 12358
    • Source: My IP (will make this instance only accessible from your current computer IP)
  24. AddRule.png


  25. Click “Review and Launch”:
  26. ReviewLaunch.png


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


  29. 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:
  30. DownloadKey.png


  31. Click on “Launch Instances”:
  32. LaunchWithKey.png


  33. You can view your instance by clicking on “View Instances”:
  34. ViewInstance.png


  35. Select the instance you just created, and give a name:
  36. RenameInstance.png


  37. 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":
  38. ElasticIP.png


  39. Click on "Allocate IP". A new public IP will be generated by Amazon:
  40. AllocateIP.png


  41. Click on "Close":
  42. NewIP.png


  43. Go to the left pane and click on "Instance". Then select the instance "FreeSBC" to display its description:
  44. IPforInstance.png


  45. 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:
  46. GetTheRightNetworkInterface.png


  47. Click on the identified Network Interface associated with the main Private IP, then click on "Interface ID" link:
  48. InterfaceID.png


  49. Right-click on the selected Network Interface, then click "Associate Address":
  50. AssociateAddress.png


  51. In the Address list, select the public IP to associate with the main Network Interface. Then, click on "Associate Address":
  52. SelectAddress.png


  53. Click on "Instances" on the left pane and select "FreeSBC" instance. Check if your instance is associated with a public IP:
  54. 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

  1. Follow the link:
  2. FailedLaunchLink.png


  3. Click on “Continue to Subscribe”:
  4. Subscribe.png


  5. 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:
  6. 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