This approach might work well in certain cases but has its limitations: ~]$ ssh -L 9090::9090 ~]$ ~]$ ssh -L 9091::9090 ~]$īob can now point his local workstation's browser to to access the web console for, and to access the web console for. Using SSH, Bob opens a TCP tunnel for both systems, pointing to the web console port (9090) for and port 9091 for. To make sure that you don't breach any rules, please consult with your IT security representative.
SSH command-line access to the database cluster is straightforward: ~]$ ssh ~]$ ssh ~]$ ~]$ ssh ~]$ ssh ~]$īut what if Bob wants to access the RHEL8 web console of and ? There are multiple ways to achieve this goal using SSH, all involving port forwarding of some sort.ĭisclaimer: In some organizations, security policies do not allow port forwarding. The firewall doesn't allow him to connect directly to this system from his workstation, but he can go through a jump server called.
For an initial analysis, he usually uses the RHEL8 web console. Let's look at the following scenario: Bob is a system administrator at Securecorp, and he just got an alert indicating that a database cluster consisting of and is performing poorly. It gets a bit more tricky when an administrator wants to break out of the command-line realm and use a web-based interface instead.
This method usually works great as long as an administrator sticks with command-line administration. Administrators first connect to a jump server using SSH, possibly through a VPN, before connecting to the target system. Many enterprises use Secure Shell (SSH) accessible jump servers to access business-critical systems.
0 kommentar(er)
