Acquiring FusionHub from AWS Marketplace (Firmware 8.0.2s127 onwards) - June 2020
[Service Interruption Notice] 03 January 2024
[Service Restored on 10 January 2034]
FusionHub is the virtual SpeedFusion appliance from Peplink which allows you to establish SpeedFusion connections between cloud servers and physical Peplink devices, among those supported is Amazon Web Services/AWS.
###A) Sample Deployment Diagram
*Additional setup network diagrams can be found here.
###B) Notes on the AWS user account access control and protection:
-
Please use the adequate account type, eg. IAM account access level, avoid using the highest level, root user for the operations.
-
Is it recommended user account with appropriate access privilege, namely, AmazonEC2FullAccess & AWSMarketplaceManageSubscriptions, to access the AWS.
###C) Prerequisite
The user who wishes to deploy FusionHub on AWS should possed some basic technical knowledge/know-how in the area listed below:
-
Understand the operation of SpeedFusion/PepVPN on Balance/MAX and FusionHub
-
Understand how to use InControl 2 (https://www.peplink.com/software/network-management-solution-incontrol-2/)
-
Understand the FusionHub license model. (Software license of FusionHub is free for 1 SpeedFusion/PepVPN Peer, it is required to purchase the license from our eStore if requires to connect more than one SpeedFusion/PepVPN peer)
-
Understand the concept and know how to operate the Amazon AWS Marketplace, EC2, VPC
-
Understand the requirement for FusionHub on AWS and which will incur changes by AWS which according to the different type of instance and regions.
-
EC2 x1
-
VPC x1
-
Elastic IP x1
-
Volume (1 GB) x1
-
###D) Deployment Steps
A typical FusionHub provisioning requires about 5 to 10 minutes to complete. Any additional settings might need more steps and a longer time.
Now you can acquire the FusionHub instance from AWS Marketplace, as illustrated with the steps below.
- Login to AWS Marketplace
- Once logged in, look for the FusionHub using the search tool
- The FusionHub will be shown in the search results page, click on the FusionHub to continue.
- Select the Region and the EC2 Instance type for your FusionHub, then click “Continue to Subscribe” for the next step.
The available regions include:
US East - N. Virginia, Ohio; US West - N. California, Oregon; Canada - Central
EU - Frankfurt, Ireland, London, Paris, Stockholm, Milan
Asia Pacific - Hong Kong, Singapore, Sydney, Seoul, Tokyo, Osaka, Mumbai
South America - Sao Paulo
Middle East - Bahrain
Africa - Cape Town
-
You may review the Terms and Conditions, then click on the “Continue to Configuration” to proceed.
-
Review the information and make the changes if needed, then click on the “Continue to Launch” for the next step.
- On the Launch this software page, you may select the “Launch through EC2” option under the “Choose Action” to continue.
Setting the Instance type
- 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.
- 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.
- 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.
- Review the settings and launch the FusionHub instance.
- 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
- 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.
- 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
- 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.
###E) Post Installation Tasks
E.1 - FusionHub - External Connectivity
Few more tasks to have the FusionHub with external connectivity.
1. Disable Source/Destination Check for FusionHub Instance
- Open the AWS Management Console.
- Select Services > EC2 > Instances.
- Select the FusionHub instance.
- Select “Action” on top of the page, choose Networking > Change Source/Destination Check.
- Click Yes/Disable.
2. Configure IP Forwarding mode for FusionHub
Enable IP Forwarding option under the Network > WAN > Connection Settings, the default Routing Mode is NAT.
E.2 - Testing Connectivity
Once you have the FusionHub setup and the SpeedFusion (VPN) configured at both FusionHub and remote peer(s), you might want to conduct some tests to ensure the SpeedFusion connectivity is working.
1. PING
There are tools built in the FusionHub, PING is one of the options to check the connectivity, it can be accessed via System > Tools > Ping, eg. remote LAN IP: 192.168.2.1.
2. PepVPN Analyzer
Go to Status > SpeedFusion, click in the “>” to launch the PepVPN Analyzer tool.
You can choose various testing options, TCP or UDP, Upload vs Download, number of streams, & duration.
E.3 - Troubleshooting Tips
Scenario 1:
If SpeedFusion is unable to connect, then you may check on the security rules, etc.
Scenario 2:
If SpeedFusion is connected, but Ping is unsuccessful, then you need to check security rules, VPC route table, etc.
###F) External Reference
Additional settings and configurations guide can be found in the FusionHub User Manual.