Testing¹ reveals that Lightsail instances in fact are EC2 instances, from the t2 class of burstable instances. EC2, of course, has many more instance families and classes other than the t2, almost all of which are more “powerful” (or better equipped for certain tasks) than these, but also much more expensive. But for meaningful comparisons, … Read more
I figured it out. I had the arguments in the wrong order. This works: scp -i mykey.pem somefile.txt root@my.ec2.id.amazonaws.com:/
Get the path of running Apache $ ps -ef | grep apache apache 12846 14590 0 Oct20 ? 00:00:00 /usr/sbin/apache2 Append -V argument to the path $ /usr/sbin/apache2 -V | grep SERVER_CONFIG_FILE -D SERVER_CONFIG_FILE=”/etc/apache2/apache2.conf” Reference: http://commanigy.com/blog/2011/6/8/finding-apache-configuration-file-httpd-conf-location
The problem is having wrong mod on the file. Easily solved by executing – chmod 400 mykey.pem Taken from AWS instructions – Your key file must not be publicly viewable for SSH to work. Use this command if needed: chmod 400 mykey.pem 400 protects it by making it read only and only for the owner.