1. SSH to the virtual machine with SSH client software

To connect from Windows to Linux on the cloud via SSH, you need to install SSH client software (such as Tera Term or putty). I used Tera Term this time.
When you create a virtual machine in the cloud, it will be issued a global IP. Set that IP address to Tera Term and connect.

The SSH authentication screen will be displayed.
Here you will perform SSH connection login work, but the SSH connection login method differs depending on the provider of each cloud.

For details, please refer to the homepage of the provider to be used.

In the case of Company A, which I used, enter the [User Name] prepared for the Linux instance, specify the [Private Key] created in advance, and log in.

2. Install VNC server and XRDP and make initial settings for VNC server

Install XRDP and VNC server (I used TigerVNC server this time) to remotely and GUI operate Linux on the cloud using “Remote Desktop Connection” installed on local Windows.

# yum -y install xrdp tigervnc-server

After that, make the initial settings for the VNC service (user name, screen size, password settings, etc.).

First, copy the VNC server configuration file.

# cp /usr/lib/systemd/system/vncserver@.service /etc/systemd/system/vncserver@:1.service

Edit the copied file.

# vi /etc/systemd/system/vncserver@:1.service

Edit <USER> to your cloud user account name and set the screen size (-geometry) as needed.

After saving, apply the changes.

# systemctl daemon-reload

Set the password for VNC connection. (It is set, but it is not used when logging in.)

First, the root password.

# vncpasswd

If you need a user other than root, use

# vncpasswd <user_name>;

Please add the VNC password in .

Next, change the default XRDP settings.

Change the color from 32bit to 24bit because the original color setting causes an error when logging in with an XRDP connection.

# vi /etc/xrdp/xrdp.ini

Change max_bpp=32 to max_bpp=24 and save.

3. Install desktop environment

Install a desktop environment to operate the GUI when logging in to Linux via remote desktop connection.

# yum groupinstall graphical-server-environment

Set the operating mode (default) at system startup to boot with GUI.

# systemctl set-default graphical.target

4. Disable firewall, disable SELinux

Since the security (virtual firewall) is set as a cloud instance (virtual machine), the firewall as Linux is disabled. (Because this is a bottleneck and I can't connect...)

turn off the firewall

Disable automatic startup of the firewall.

# systemctl stop firewalld # systemctl disable firewalld

Check the status with the following command.

# systemctl status firewalld

Also disabled SELinux as it can cause XRDP boot failures. This is Hanako's little point ♪

To disable SELinux, edit the configuration file,

# vi /etc/selinux/config

Change SELINUX=enforcing to SELINUX=disabled.

Apply changes immediately after saving.

# systemctl daemon-reload

After rebooting the system, check the SELinux status and make sure it is Disabled.

# getenforce Disabled

5. Set a password for the virtual machine

Use this username and password to log in when you make a remote desktop connection to your virtual machine on the cloud.

First set the root password.

# passwd

If you use a user account

# passwd <user_name>;

6. Start VNC server and XRDP

Set the VNC server to start automatically.

# systemctl enable vncserver@:1.service

Start a VNC server.

# systemctl start vncserver@:1.service

Check the status to see if the VNC server has started.

# systemctl status vncserver@:1.service

Next, set the automatic startup of XRDP.

# systemctl enable xrdp.service

Start XRDP.

# systemctl start xrdp.service

Check the status to see if XRDP has started.

# systemctl status xrdp.service

After confirming that the VNC server and XRDP have started, the work of Tera Term is complete.

Then RDP from your local to the cloud machine.

I tried running the FPGA development tool Quartus Prime on the cloud server [#2/2]

In recent years, when trying to build a development environment for Intel's FPGAs and CPLDs, it is necessary to prepare a reasonably high-spec personal computer in order to use the development software Quartus® Prime. One of the requirements is that the CPU must be a 64bit type!

As of 2017, Quartus® Prime cannot be installed on a 32bit machine environment.
If there is insufficient memory or disk space, you can increase it somehow, but the CPU does not work that way.

For users who don't have a PC with suitable specs but want to play around with an FPGA for a while, the "CPU wall" stands in their way.
We want more users to feel free to use Quartus® Prime! With that in mind, I installed Quartus® Prime Lite Edition on the cloud.

Click here for recommended articles/materials
The real introduction: Part 1. Creating an environment to start development
Quartus - Supported Windows OS Compatibility Chart
Quartus - Supported Devices Correspondence Table

Or from another point of view, when preparing a high-spec machine that can compile Stratix® 10, Arria® 10, etc., there is an option to consider a cloud virtual machine instead of purchasing a physical computer. I think there will be in the future.

I would appreciate it if you could refer to something.

Click here for recommended articles/materials

I tried running the FPGA development tool Quartus Prime on the cloud server [#2/2]
The first LED blinking with FPGA!
The real introduction: Part 1. Creating an environment to start development
Quartus - Supported Windows OS Compatibility Chart
Quartus - Supported Devices Correspondence Table