With Google&rsquo;s new release of an SSL Certificates having a small ranking boost on search engine ranking, we&rsquo;ve decided to release an easy tutorial on installing the ssl certificates on an Amazon EC2 Ubuntu server.

For those wanting to check their version of Ubuntu you can run:

<pre class="wp-block-code"><code>lsb_release -a</code></pre>

This is what ours returned:

<pre class="wp-block-code"><code>No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.5 LTS
Release:	18.04
Codename:	bionic</code></pre>

So let&rsquo;s dive into what needs to be done to install Standard SSL Certificate with Amazon EC2.

<h2>MOVE SSL CERTIFICATES FILES TO SERVER</h2>

You need to move your ssl files to server. Follow the following steps.

1. SSH to your server

<pre class="wp-block-code"><code>ssh -i yourkey.pem ubuntu@your_server_ip_or_domain</code></pre>

2. Go to your html folder &amp; make a folder to hold the ssl files

<pre class="wp-block-code"><code>cd /var/www/html
sudo mkdir ssl_files</code></pre>

3. Now go to your folder in which ssl files are stored on your local machine &amp; open the terminal <code>CTRL+ALT+T on Ubuntu</code>

4. Move the files to server via <a href="https://tcmhack.in/how-to-upload-files-via-ssh-using-scp-on-ubuntu/">Secure Copy Protocal (SCP)</a> to your newly created folder i.e <code>ssl_files</code>. Don't know how to use SCP? <a href="https://tcmhack.in/how-to-upload-files-via-ssh-using-scp-on-ubuntu/">Click here</a>

6. Now SSH again to your server and move the certificate files to required place.

<pre class="wp-block-code"><code>ssh -i yourkey.pem ubuntu@your_server_ip_or_domain
cd /var/www/html/ssl_files

sudo cp your_site.crt /etc/apache2/ssl/your_site.crt
sudo cp your_site.key /etc/apache2/ssl/your_site.key
sudo cp your_site.ca-bundle /etc/apache2/ssl/your_site.ca-bundle</code></pre>

<h2>ADDING SSL VIRTUALHOST ENTRIES</h2>

At this point, all we need to do is enable the VHOST for our site to render the SSL pages. You will either need to create a new VHOST entry if its a new site, or add this to an existing entry for your site.

<pre class="wp-block-code"><code>&lt;VirtualHost *:443&gt;
 ServerName your_site.com
 ServerAlias www.your_site.com
 DocumentRoot /documentroot/
 SSLEngine on
 SSLCertificateFile /etc/apache2/ssl/your_site.crt
 SSLCertificateKeyFile /etc/apache2/ssl/private/your_site.key
 SSLCertificateChainFile /etc/apache2/ssl/your_site.ca-bundle
&lt;/VirtualHost&gt;</code></pre>

Restart the apache:

<pre class="wp-block-code"><code>sudo systemctl restart apache2</code></pre>

<h2>ENABLE APACHE 2 SSL MODULE IF NOT ENABLED ALREADY</h2>

Next thing to do if you haven&rsquo;t already is to enable the SSL module for Apache and then restarting apache. This is as simple as typing:

<pre class="wp-block-code"><code>sudo a2enmod ssl
sudo systemctl restart apache2</code></pre>

<h2>ENABLE SSL TRAFFIC ON AMAZON EC2</h2>

One last step is to ensure SSL traffic is enabled or your security group in Amazon. By default, Amazon does not enable this as not all sites will need it. Log in to your Amazon account, go to EC2 and your server instance. From their click on the Security Group assigned to your site, and enable HTTPs traffic for Inbound.
<img src="../../../../uploads/1744733376731-amazon-enabled-https-traffic.jpg" alt="" width="780" height="251">

Load your site and you should now be able to run https! Just make sure to redirect any http url&rsquo;s to https, so your not serving the same content up twice by mistake, as this would be bad for SEO and hurt your Google rankings. One main reason to add SSL is for Google rankings &mdash; we don&rsquo;t want to gain a little, and lose our seo by serving duplicate content.

That's it. If you're still facing the issues? feel free to ask the questions in comment section.

With Google’s new release of an SSL Certificates having a small ranking boost on search engine ranking, we’ve decided to release an easy tutorial...

How to install SSL Certificates on Amazon EC2 Ubuntu Server - TCMHACK

How to install SSL Certificates on Amazon EC2 Ubuntu Server

A crontab file contains instructions for the&nbsp;cron daemon in the following simplified manner: "run this command at this time on this date". Each user can define their own crontab. Commands defined in any given crontab are executed under the user who owns that particular crontab. Uucp and News usually have their own crontabs, eliminating the need for explicitly running su as part of a cron command.

Blank lines, leading spaces, and tabs are ignored. Lines whose first non-white space character is a pound-sign (#) are comments, and are not processed. Note that comments are not allowed on the same line as cron commands, since they are considered a part of the command. Similarly, comments are not allowed on the same line as environment variable settings.

An active line in a crontab is either an environment setting or a cron command. An environment setting is of the form:

<pre class="wp-block-preformatted">name = value</pre>

where the white spaces around the equal-sign (=) are optional, and any subsequent non-leading white spaces in value is a part of the value assigned to name. The value string may be placed in quotes (single or double, but matching) to preserve leading or trailing white spaces.

Several environment variables are set up automatically by the cron daemon. SHELL is set to /bin/sh, and LOGNAME and HOME are set from the /etc/passwd line of the crontab&acute;s owner. HOME and SHELL can be overridden by settings in the crontab; LOGNAME can not.

(Note: the LOGNAME variable is sometimes called USER on BSD systems and is also automatically set).

In addition to LOGNAME, HOME, and SHELL, cron looks at the MAILTO variable if a mail needs to be send as a result of running any commands in that particular crontab. If MAILTO is defined (and non-empty), mail is sent to the specified address. If MAILTO is defined but empty (MAILTO=""), no mail is sent. Otherwise, mail is sent to the owner of the crontab. This option is useful if you decide to use /bin/mail instead of /usr/lib/sendmail as your mailer. Note that /bin/mail does not provide aliasing and UUCP usually does not read its mail. If MAILFROM is defined (and non-empty), it is used as the envelope sender address, otherwise, ``root'' is used.

By default, cron sends a mail using the 'Content-Type:' header of 'text/plain' with the 'charset=' parameter set to the 'charmap/codeset' of the locale in which crond is started up, i.e., either the default system locale, if no LC_* environment variables are set, or the locale specified by the LC_* environment variables. Different character encodings can be used for mailing cron job outputs by setting the CONTENT_TYPE and CONTENT_TRANSFER_ENCODING variables in a crontab to the correct values of the mail headers of those names.

The CRON_TZ variable specifies the time zone specific for the cron table. The user should enter a time according to the specified time zone into the table. The time used for writing into a log file is taken from the local time zone, where the daemon is running.

The MLS_LEVEL environment variable provides support for multiple per-job SELinux security contexts in the same crontab. By default, cron jobs execute with the default SELinux security context of the user that created the crontab file. When using multiple security levels and roles, this may not be sufficient, because the same user may be running in different roles or in different security levels.

The RANDOM_DELAY variable allows delaying job startups by random amount of minutes with upper limit specified by the variable. The random scaling factor is determined during the cron daemon startup so it remains constant for the whole run time of the daemon.

The time and date fields are:

<pre class="wp-block-code"><code>field allowed values
----- --------------
minute 0-59
hour 0-23
day of month 1-31
month 1-12 (or names, see below)
day of week 0-7 (0 or 7 is Sunday, or use names)</code></pre>

A field may contain an asterisk (*), which always stands for "first-last".

Ranges of numbers are allowed. Ranges are two numbers separated with a hyphen. The specified range is inclusive. For example, 8-11 for an 'hours' entry specifies execution at hours 8, 9, 10, and 11. The first number must be less than or equal to the second one.

Lists are allowed. A list is a set of numbers (or ranges) separated by commas. Examples: "1,2,5,9", "0-4,8-12".

<h4>EXAMPLE CRON FILE</h4>

<pre class="wp-block-code"><code># use /bin/sh to run commands, no matter what /etc/passwd says
SHELL=/bin/sh
# mail any output to `paul', no matter whose crontab this is
MAILTO=paul
#
CRON_TZ=Japan
# run five minutes after midnight, every day
5 0 * * * $HOME/bin/daily.job &gt;&gt; $HOME/tmp/out 2&gt;&amp;1
# run at 2:15pm on the first of every month -- output mailed to paul
15 14 1 * * $HOME/bin/monthly
# run at 10 pm on weekdays, annoy Joe
0 22 * * 1-5 mail -s "It's 10pm" joe%Joe,%%Where are your kids?%
23 0-23/2 * * * echo "run 23 minutes after midn, 2am, 4am ..., everyday"
5 4 * * sun echo "run at 5 after 4 every sunday"</code></pre>

<h4>Jobs in /etc/cron.d/</h4>

The jobs in cron.d and /etc/crontab are system jobs, which are used usually for more than one user, thus, additionally the username is needed. MAILTO on the first line is optional.

<h4>EXAMPLE OF A JOB IN /etc/cron.d/job</h4>

<pre class="wp-block-code"><code>#login as root
#create job with preferred editor (e.g. vim)
MAILTO=root
* * * * * root touch /tmp/file</code></pre>

<h4>SELinux with multi level security (MLS)</h4>

In a crontab, it is important to specify a security level by crontab -s or specifying the required level on the first line of the crontab. Each level is specified in /etc/selinux/targeted/seusers. When using crontab in the MLS mode, it is especially important to:

<ul>
<li>check/change the actual role,</li>
<li>set correct role for directory, which is used for input/output.</li>
</ul>

<h4>EXAMPLE FOR SELINUX MLS</h4>

<pre class="wp-block-code"><code># login as root
newrole -r sysadm_r
mkdir /tmp/SystemHigh
chcon -l SystemHigh /tmp/SystemHigh
crontab -e
# write in crontab file
MLS_LEVEL=SystemHigh
0-59 * * * * id -Z &gt; /tmp/SystemHigh/crontest</code></pre>

<h4>FILES</h4>

<ul>
<li>/etc/crontab main system crontab file.</li>
<li>/var/spool/cron/ a directory for storing crontabs defined by users.</li>
<li>/etc/cron.d/ a directory for storing system crontabs.</li>
</ul>

<h4>EXTENSIONS</h4>

These special time specification "nicknames" which replace the 5 initial time and date fields, and are prefixed with the '@' character, are supported:

<pre class="wp-block-code"><code>@reboot : Run once after reboot.
@yearly : Run once a year, ie. "0 0 1 1 *".
@annually : Run once a year, ie. "0 0 1 1 *".
@monthly : Run once a month, ie. "0 0 1 * *".
@weekly : Run once a week, ie. "0 0 * * 0".
@daily : Run once a day, ie. "0 0 * * *".
@hourly : Run once an hour, ie. "0 * * * *".</code></pre>

A crontab file contains instructions for the cron daemon in the following simplified manner: "run this command at this time on this date". Each user can define their own crontab. Commands defined in any given crontab are executed under the user who owns that particular crontab.

What is Crontab?

Hey Guys, In this tutorial, we will learn how to upload files via ssh using terminal.

Uploading files via ssh required when you don't have any cPanel to work with like aws hosting which only provides you the SSH.

So we will be using the SCP (Secure Copy Protocal) for file transfer. Let's start.

<h3>What is Secure Copy Protocal (SCP)</h3>

Secure copy protocol (SCP) is a means of securely transferring computer files between a local host and a remote host or between two remote hosts.It is based on the Secure Shell (SSH) protocol.

"SCP" commonly refers to both the Secure Copy Protocol and the program itself. According to OpenSSH developers in April 2019 the scp protocol is outdated, inflexible and not readily fixed; they recommend the use of more modern protocols like sftp and rsync for file transfer.

The SCP program is a software tool implementing the SCP protocol as a service daemon or client. It is a program to perform secure copying.

<h4>Syntax</h4>

Typically, a syntax of&nbsp;scp&nbsp;program&nbsp;is like the syntax of&nbsp;cp&nbsp;(copy):

Copying file to host:

<pre class="wp-block-code"><code>scp SourceFile user@host:directory/TargetFile</code></pre>

Copying folder from host:

<pre class="wp-block-code"><code>scp user@host:directory/SourceFile TargetFile
scp -r user@host:directory/SourceFolder TargetFolder</code></pre>

Note that if the remote host uses a port other than the default of 22, it can be specified in the command. For example, copying a file from host:

<pre class="wp-block-code"><code>scp -P 2222 user@host:directory/SourceFile TargetFile</code></pre>

If you're working with aws hosting then you must have to use the key

<pre class="wp-block-code"><code>scp -i yourkey.pem user@host:directory/SourceFile TargetFile</code></pre>

Let's take an example:

<pre class="wp-block-code"><code>scp -i mykey.pem /var/www/html/myfile.sql ubuntu@google.com:/var/www/htmlmyfile.sql</code></pre>

<h4>Feels like watching?</h4>
<iframe style="width: 678px; height: 381px;" title="YouTube video player" src="https://www.youtube.com/embed/C0ImnCTI1W8?si=2ZMlGpmugDBo_Qrc" width="678" height="381" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen="allowfullscreen" referrerpolicy="strict-origin-when-cross-origin"></iframe>

Hey Guys, In this tutorial, we will learn how to upload files via ssh using terminal.



Uploading files via ssh required when you don't have any...

How to upload files via ssh using scp on ubuntu - TCMHACK

How to upload files via ssh using scp on ubuntu

Uploading files on AWS S3 is very easy with AWS Javascript SDK. We're going to upload files to S3 in some simple steps.
Before going to next steps, I'm assuming you already have a file stored in fileToBeUpload variable in Javascript.
Let's Begin.
<h3>Step 1: Add the AWS SDK into the head section of your file.</h3>
<pre class="wp-block-preformatted">&lt;script src="<a href="https://sdk.amazonaws.com/js/aws-sdk-2.1.24.min.js">https://sdk.amazonaws.com/js/aws-sdk-2.207.0.min.js</a>"&gt;&lt;/script&gt; </pre>
<h3>Step 2: Initiate the AWS Configuration.</h3>
There are two to initialize the AWS Configuration.
A. By using the AWS Key &amp; Secret Key but it is not advisable to display your keys directly on page.
<pre class="wp-block-preformatted">&lt;script type="text/javascript"&gt;
&nbsp; &nbsp; AWS.config.update({
&nbsp; &nbsp; &nbsp; &nbsp; accessKeyId: 'AWS_ACCESS_KEY',
&nbsp; &nbsp; &nbsp; &nbsp; secretAccessKey: 'AWS_SECRET_KEY',
 region: 'AWS_REGION'
&nbsp; &nbsp; });
&lt;/script&gt;</pre>
B. By using the AWS Identity Pool Id (I recommand using the identityPoolId)
<pre class="wp-block-preformatted">&lt;script type="text/javascript"&gt;
&nbsp; &nbsp; AWS.config.update({
&nbsp; &nbsp; &nbsp; &nbsp; credentials: new AWS.CognitoIdentityCredentials({
 IdentityPoolId: 'AWS_Identity_Pool_Id'
 }),
 region: 'AWS_REGION'
&nbsp; &nbsp; });
&lt;/script&gt;</pre>
<h3>Step 3: Lets start the uploading</h3>
<div>
<pre>var bucketName = "AWS_BUCKET_NAME"; var fileToBeUpload = "FILE_TO_BE_UPLOAD"; var filePath = "demo/user_uploaded/"; // File will be saved to this folder on aws s3. // Initialize the AWS Object var bucket = new AWS.S3({ apiVersion: "2006-03-01", params: { Bucket: bucketName }, }); var params = { Key: filePath, ContentType: fileToBeUpload.type, Body: fileToBeUpload, ContentDisposition: "attachment", // if you want to enable file download via public url. }; /* turn off the timeout (Optional) */ AWS.config.httpOptions.timeout = 0; // upload file bucket.upload(params).on("httpUploadProgress", function (evt) { var uploaded = Math.round((evt.loaded / evt.total) * 100); console.log("File uploaded", uploaded, "%"); }) .send(function (err, data) { if (err) { // an error occurred, handle the error console.log(err, err.stack); return; } var fileUrl = data.Location; console.log("File URL:", fileUrl); alert("File is uploaded successfully!"); });</pre>
</div>
To upload the file successfully, you need to enable CORS configuration on S3.
Please comment below if you have any question.

Uploading files on AWS S3 is very easy with AWS Javascript SDK. We're going to upload files to S3 in some simple steps...

How to install SSL Certificates on Amazon EC2 Ubuntu Server

What is Crontab?

How to upload files via ssh using scp on ubuntu

AWS S3 file upload with progress bar using javascript sdk