RPort
Search…
RPort
RPort Knowledge Base
👀
WHAT IS RPORT
Features and benefits of RPort
🚀
GETTING STARTED
Install the RPort Server
Launch RPort in the cloud
Install on-premises
Install on Vultr
Install on Azure
Install on AWS EC2
Install on Digital Ocean
Install on Scaleway
Install on Google Compute
Install on Hetzner Cloud
Install RPort on any virgin cloud VM
Change the FQDN of the RPort server
Enable two factor authentication
Log in with 2FA
Connecting Clients
Using the remote access
Renaming and tagging of clients
Organize clients with groups
Activate the vault
🗣️ NEED HELP?
Troubleshoot common problems
Request Support
🔦
DIGGING DEEPER
Using the API
RPort Technology Explained
Commands and Scripts
Client Configuration Options
Advanced client management
Updating RPort
Backing up the rport server
Powered By GitBook
Install on AWS EC2
get your RPort Server up and running in less than 5 minutes on your own EC2 instance.

Start a new instance

Do not install the RPort server on an existing instance where other applications are already running. You will very likely create conflicts.
Because RPort has almost no dependencies it will run flawlessly on any halfway modern Linux. We recommend using Debian 10. Debian is lightweight and secure.
  • Log in to your AWS console, go to ECS and select your preferred region.
  • Click "Launch Instances" and type "Debian" into the search bar. Select 64-bit (x86) and click the blue Select button.
Select a Debian Instance
The RPort server doesn't require a lot of CPU, disk, or memory resources. Selecting a t2.micro instance is perfect. ✋Do not launch the instance yet. Click "Next: Configure Instance Details".
Select a micro instance.
On "Step 3: Configure Instance Details" you don't have to change anything. Take over all the pre-selected defaults. Click "Next: Add Storage".
On "Step 4: Add Storage" you don't have to change anything. 8 GiB is fairly enough disk storage. Take over all the pre-selected defaults. Click "Next: Add Tags".
On "Step 5: Add Tags" you don't have to change anything. But feel free to add tags to keep your ECS instance well organized. Click "Next: Configure Security Group".
On "Step 6: Configure Security Group" setting up the security group is crucial. Enter the following settings.
Type
Protocol
Port Range
Source
Description
SSH
TCP
22
0.0.0.0/0
SSH
All ICMP -IPv4
ICMP
0-65535
0.0.0./0, ::/0
ICMP PING
HTTP
TCP
80
0.0.0./0, ::/0
HTTP
HTTPS
TCP
443
0.0.0./0, ::/0
HTTPS
Custom TCP
TCP
20000-30000
0.0.0./0, ::/0
RPort Tunnel Range
Security Group
Do not skip the ICMP IPv4 rule. Your server must respond to ICMP ping echo requests. Otherwise, the automated setup of DNS and SSL will fail.
After creating the security group click "Review and launch".
Don't worry about the warning "Your security group, RPort Server, open to the world. That's intended.
Now click "Launch" to launch the instance. On the last step select which SSH keys to use. The decision is up to you. Finally, launch the instance.

Install the RPort server on your new ECS2 instance

From the list of instances grab the public ipv4 address of your newly created instance.
Grab the IP address of the new instance.
Connect over SSH to the instance using the admin user. Usually, you must specify the private key created for the instance or the region. For example ssh -i .ssh/ec2-ohio.pem [email protected]
After the login, change to the root account by typing in sudo -i.
Previous
Install on Azure
Next
Install on Digital Ocean
Last modified 6mo ago
Export as PDF
Copy link
Contents
Start a new instance
Install the RPort server on your new ECS2 instance