Deploying Peplink FusionHub at AWS Marketplace

Acquiring FusionHub from AWS Marketplace (Firmware 8.0.2s127 onwards) - June 2020

Now you can acquire the FusionHub instance from AWS Marketplace, as illustrated with steps below.

  1. Login to AWS Marketplace

  1. Once logged in, look for the FusionHub using the search tool

  1. The FusionHub will be shown in the search results page, click on the FusionHub to continue.

  1. Select the Region and the EC2 Instance type for your FusionHub, then click “Continue to Subscribe” for the next step.

  1. You may review the Terms and Conditions, then click on the “Continue to Configuration” to proceed.

  2. Review the information and make the changes if needed, then click on the “Continue to Launch” for the next step.

  1. On the Launch this software page, you may select the “Launch through EC2” option under the “Choose Action” to continue.

Setting the Instance type

  1. Choose an Instance Type that suit your deployment requirements, eg. t3.medium, then click “Next: Configure Instance Details” to proceed. You may refer to the Recommended AWS Instances guide under the FusionHub product page for more information about the sizing guide.

  1. Configure the relevant parameters. Eg. Network and Subnet (assuming you have already created the VPC with relevant settings in place), if you’re unsure what these should be, then please skip this step and click “Review and Launch” at the bottom right, else continue with “Next: Add Storage” button.

  1. To ensure the FusionHub default services are accessible once it is provisioned, please check on the filtering rules that automatically associated to the FusionHub, click “Review and Launch” to start the FusionHub.

  1. Review the settings and launch the FusionHub instance.

  1. The FusionHub instance has been launched, you may click on the “View Instances” to check on the FusionHub status

Retrieving the default password and associating the Public IP

  1. Do take note of the Instance ID, it is the default password for this particular FusionHub instance. Next, assign a Public IP so the FusionHub can be accessed from the Internet and ready for SpeedFusion configuration. Select the Action > Networking > Manage IP Address to continue.

  1. A new browser tab will appear. You can associate the Public IP to the FusionHub instance at this page. This Public IP (Elastic IP address) will be used for accessing the FusionHub - Web Admin, as described in the next section.

Accessing FusionHub

  1. Now, you may access your FusionHub from anywhere in the Internet, in your web browser, type in “https://[FusionHub.instance.public.ip.address]” in order to access FusionHub’s administration interface. Remember the default password is the Instance ID.

Now, you may continue with the FusionHub activation and setup tasks after successful login.

5 Likes

Hey @WeiMing
Have used this many time since it was launched and absolutely love it!
One thing we have noticed is every second or third time, the Instance ID does not work as the password but “admin” does

I have no problem to login with the instance ID as a password. I tested it many times.

Please help to open ticket for us take a look of your FusionHub.

1 Like

No issue for me either…

1 Like

Ok, just to clarify, this is what is happening;
-Create FusionHub Solo Licence and add serial number to InControl2 account
-Launch FusionHub via AWS Marketplace
-Login to FusionHub via public IP address using admin/admin (Instance ID does not work)
-Go through setup and apply FusionHub licence key
-FusionHub reboots
-Finished setup via remote web admin from InControl2
-Today I tried login in with admin/admin and it didn’t work but admin/instance ID did work.

My question is, should the Instance ID be the password immediately or does this not happen until after the licence key is applied?

@Harry_Thompson, the instance ID will be the password before or after the license key is applied.

1 Like

This is not what we are seeing.
At least 5 times I have only been able to log in using admin/admin for marketplace launched instances.
I’ll do some testing tomorrow

Just spun up with these instructions on Oct 19 on Oregon server - same results. Initial user name and password combo was admin/admin

@Sean_Rabbitt, please open ticket for us to take a look. Thanks.