FreeSBC:Cloud:AWS Installation

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.

Instantiate an FreeSBC

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






2. On the left menu, click on “AMIs”:






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






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






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






6. Click “Configure instance Details”:






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






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






9. Click “Add Storage”:






10. Change the volume Size to 40GiB. Then, click “Add Tags”:






11. You can leave the default parameters as they are. Then, click “Configure Security Group”:






12. 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)






13. Click “Review and Launch”:






14. 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:






15. 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:






16. Click on “Launch Instances”:






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






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






19. 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":






20. Click on "Allocate IP". A new public IP will be generated by Amazon:






21. Click on "Close":






22. Go to the left pane and click on "Instance". Then select the instance "FreeSBC" to display its description:






23. 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:






24. Click on the identified Network Interface associated with the main Private IP, then click on "Interface ID" link:






25. Right-click on the selected Network Interface, then click "Associate Address":






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






27. Click on "Instances" on the left pane and select "FreeSBC" instance. Check if your instance is associated with a public IP:

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

1. Follow the link:






2. Click on “Continue to Subscribe”:



3. 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:

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