Terry's questions

I need to install Grass GIS on my Amazon Linux 2 AMI instance which is of type t2.small During the configuration of Grass GIS it stopped with

checking for GL/gl.h... no
configure: error: *** Unable to locate OpenGL includes.

To install OpenGL and/or its includes, I've tried following (all with sudo)

yum install libx11-dev
yum install libx11
yum install libX11
yum install libX11-dev
yum install libglu1-mesa-dev
yum install freeglut-devel
yum install freeglut3-dev
yum install mesa-common-dev

As far as I can remember, all of them returned a message of this kind (message translated into English)

amzn2-core
no package named libX11-dev which can be used

Question #1

I kept on searching and found this post which seems to say that in order to use OpenGL, the instance type should be G2 Is that right?

If that's the case then I presume that the G2 type has a capable graphics hardware whereas my instance t2.small (or shortlyT2 ?) is likely to have no capable graphics hardware.

lspci | grep VGA gives: 00:02.0 VGA compatible controller: Cirrus Logic GD 5446

Question #2

Is it in any way possible to install OpenGL on t2.type (whether using yum or using the source codes and building OpenGL from scratch) ?

Last week I've created an AWS Instance using the Ubuntu Server 20.x AMI. It had yum built-in. Today I've deleted that instance and created a new Instance using the same AMI. After I've launched the Instance I've noticed the welcome screen was substantially different and the default (the AWS given) user name was different too. The UN on previous Instance was ec2-user whereas in this Instance it is ubuntu After I logged in over ssh and typed yum it said Command 'yum' not found

Question: I'd like to create the same type Instance which I created last week. How can I do it?

Here are the Screenshots of the welcome screens of the previous and the current Instances.

EC2 (In this screenshot when I took it the root user was seen. It had ec2-useras default)

Ubuntu

I've installed nginx on AWS using this configure script

--prefix=/usr/local/nginx-1.16.1 --with-http_ssl_module --with-openssl=~/Downloads/openssl-1.1.1i --without-http_rewrite_module

and I've issued a Certificate for my URL (let it be mydom.com) using the AWS Certificate Manager (ACM) and its status is displayed as Issued Then I've edited the relevant section in the nginx.conf

server {
listen 443 ssl;
server_name localhost mydom.com;
ssl_certificate  /etc/ssl/certs/ca-bundle.crt;
ssl_certificate_key  /etc/trusted-key.key;
<truncated>
}

I've selected the files: /etc/ssl/certs/ca-bundle.crt and /etc/trusted-key.key only because they were there on the Linux File System and just for the sake of trying to see if nginx would run with them but it didn't run. It gave:

[emerg] cannot load certificate key "/etc/trusted-key.key": PEM_read_bio_PrivateKey() failes (SSL: error:0909006C:PEM routines:get_name: no start line:Expecting: ANY PRIVATE KEY)

Of course that was just a try. Otherwise I think I should probably use the .crt file issued by the ACM (if there are any) and then I should somehow create a .key file and put them somewhere in the Linux File System, like under the /etc/nginx/ssl? I'm not sure. How should I proceed?

Note: I have some experience running web applications on my own web server but using only the http I haven't much experience with https