Linux Server Configuration

Udacity Fullstack Nanodegree - Project 3

Introduction

What is this project about?

This project is linked to the 5th module of the Udacity Fullstack Nanodegree, the "Deploying to Linux Servers" course. The course teaches the basics of Linux & how to set up and secure a Linux server on the web. The goal and final project of the Nanodegree is to get a web application running live on a secure web server.

This README.md covers how the application from the 2nd project of the same nanodegree (available in this repository) was deployed on an Amazon Lightsail hosted Ubuntu Linux server.

How is this document structured?

This README.md broadly follows the 5 steps described in Udacity's "Project Details" which are necessary to pass the project:

Get a server
Secure the server
Give access to a grader user
Prepare deployment of application
Deploy application to server

Get a server

This part had 2 requirements:

Start an Ubuntu Linux server instance on Amazon Lightsail.
SSH into the server

Start an Ubuntu Server

I followed Udacity's recommendation and registered on Amazon Lightsail. After verification, I created an Ubuntu 16.04 instance in AWS Frankfurt data center.

The server is currently (July 2019) available under the public IP 18.197.158.41 and the host name ec2-18-197-158-41.eu-central-1.compute.amazonaws.com. Since AWS only provides one free month of hosting, the application will not be available post summer 2019.

SSH into the server

For Linux-based instances, Lightsail uses Secure SHell (SSH) to connect to an server instance. SSH uses a key pair (a public key and a private key) to match the remote server to an authorized user. Lightsail's account page offers a download option for the default SSH key pair. The file name is based on the region so that my instance of the file was called LightsailDefaultKey-eu-central-1. I use this name in the following steps:

Move file LightsailDefaultKey-eu-central-1 from the local machine's Download folder to the .ssh folder and rename it to udacity_key.rsa. Shell command: $ mv ~/Downloads/LightSailDefaultKey-eu-central-1 ~/.ssh/udacity_key.rsa$
Change the access permission to the file to let only the owner write and read with the change mode 600 flag. Shell command: chmod 600 ~/.ssh/udacity_key.rsa
SSH into the server with the default ubuntu user & the server's public IP address. Use the -i option flag to signal that it's an integer. Shell command: ssh -i ~/.ssh/udacity_key.rsa [email protected]

At this point, the command prompt should change to [email protected]:~$ (depending on prompt customizations)

Secure the server

This part had 3 requirements:

Update all currently installed packages.
Change the SSH port from 22 to 2200. Make sure to configure the Lightsail firewall to allow it.
Configure the Uncomplicated Firewall (UFW) to only allow incoming connections for SSH (port 2200), HTTP (port 80), and NTP (port 123).

Update packages

To update the currently installed packages, 2 commands were run:

Update the list of available packages and their versions Shell command: sudo apt-get update
Upgrade to newer versions of packages: Shell command: sudo apt-get upgrade

Change SSH Port

Disclaimer by Udacity: "When changing the SSH port, make sure that the firewall is open for port 2200 first, so that you don't lock yourself out of the server. When you change the SSH port, the Lightsail instance will no longer be accessible through the web app 'Connect using SSH' button. The button assumes the default port is being used. There are instructions on the same page for connecting from your terminal to the instance. Connect using those instructions and then follow the rest of the steps."

To change the SSH port 5 steps are needed:

Edit the sshd_config file inside the host specific configuration files /etc/ssh/sshd_config. Shell command: $ sudo nano /etc/ssh/sshd_config
Inside the file change the port number from the default 22 to 2200 and disable root login by setting PermitRootLogin to no
Save and exit the file (i.e. type CTRL+X, confirm changes with y, confirm name with Enter).
Restart the SSH connection Shell command: $ sudo service ssh restart

Configure Uncomplicated Firewall

Configure the Uncomplicated Firewall (UFW) to only allow incoming connections for SSH (port 2200), HTTP (port 80), and NTP (port 123).

$ sudo ufw allow 2200/tcp
$ sudo ufw allow 80/tcp
$ sudo ufw allow 123/udp
$ sudo ufw deny 22$
$ sudo ufw enable

Give grader access

Giving the grader access to the application via SSH requires 4 steps:

Create a new user account named grader
Give grader permission to sudo
Create an SSH key pair for grader using the ssh-keygen tool.
Log in as new grader user via SSH
Disable password authentication

Create new user

To create a new user run the command $ sudo adduser grader. The setup requires the setup of a password, which is shared with the Udacity team in a private note.
To give the new grader user the permission to sudo run the command $ sudo visudo. Below the line root ALL... add a new line grader ALL=(ALL:ALL) ALL. Save and exit the file.
Create a SSH key pair for grader using the ssh-keygen tool on the local machine. In a separate terminal window, run these commands to generate a new key:

cd ~/.ssh ssh-keygen -f ~/.ssh/grader_key.rsa
grader
*PASSWORD*
cat ~/.ssh/grader_key.rsa.pub

The content of this document has to be copied inside the authorized_keys folder on the Ubuntu server. On the remote machine run the command touch /home/grader/.ssh/authorized_keys and copy+paste the key. To protect the folder from unauthroized edits, change the access permission with the commands:

$ sudo chmod 700 /home/grader/.ssh 
$ sudo chmod 644 /home/grader/.ssh/authorized_keys
$ sudo chown -R grader:grader /home/grader/.ssh
$ sudo service ssh restart

Log into the remote VM as the new grader user with the command ssh -i ~/.ssh/grader_key.rsa -p 2200 [email protected]. The command prompt should change to [email protected]:~$ (depending on prompt customizations).
To enforce SSH key based auhentication, open the sshd config file with $ sudo nano /etc/ssh/sshd_config and edit the line PasswordAuthentication to no. Restart with $ sudo service ssh restart.

Prepare deployment

This stage required 4 steps:

Configure the local timezone to UTC.
Configure Locale
Install and configure Apache to serve a Python mod_wsgi application.
Install PostgreSQL
Install git, Flask

Configuring Time Zone

To set the timezone to UTC, run the command $ sudo dpkg-reconfigure tzdata and choose None of the above from the initial selection. Then choose UTC in the new window.

Configuring Locale Setting

I was running into an error unsupported locale setting and ran the following commands based on a stackoverflow answer by Muhammad Hassan: export LC_ALL="en_US.UTF-8", export LC_CTYPE="en_US.UTF-8", $ sudo dpkg-reconfigure locales

Install and configure Apache

To install apache2 run the command $ sudo apt-get install apache2. When navigating to the public IP of the project, the server should not show a default apache page similar to this one:

Due to the upcoming deprecation of Python2 I decided to re-write my project submission for the 2nd project in Python3. This requires a Python3 mod_wsgi package that's installed as follows:

$ sudo apt-get install libapache2-mod-wsgi-py3
$ sudo a2enmod wsgi
$ sudo service apache2 start

Install PostgreSQL

To install PostgreSQL run these commands

$ sudo apt-get install libpq-dev python-dev
$ sudo apt-get install postgresql postgresql-contrib

Install git

Run the follow command: $ sudo apt-get install git. Configure git with your credentials. If you have no experience with Git, this free Udacity course is helpful

Deploy the application

The final stage required 7 steps:

Cloning the application from Github
Updating the app code
Install virtual environment
Install necessary packages
Configure virtual host
Configure DB
Configure Google OAuth

Clone Application

Create a new directory for the app and change the access permissions:

$ sudo mkdir /var/www/catalog
$ sudo chown -R grader:grader catalog

Move into the directory and clone the application from Github:

$ cd /var/www/catalog
$ git clone https://github.com/nckre/Udacity-FullstackND-Project2-ItemCatalog.git catalog

Create a catalog.wsgi file and paste the following content via $ sudo nano /var/www/catalog/catalog.wsgi:

activate_this = '/var/www/catalog/catalog/venv3/bin/activate_this.py'
with open(activate_this) as file_:
    exec(file_.read(), dict(__file__=activate_this))

#!/usr/bin/python3
import sys
import logging
logging.basicConfig(stream=sys.stderr)
sys.path.insert(0, "/var/www/catalog/catalog/")
sys.path.insert(1, "/var/www/catalog/")

from catalog import app as application
application.secret_key = 'super_secret_key'

Update App Code

The app will require several changes to run on a webserver:

Change name from project.py to __init__.py
Edit the app to make the following changes (user CTRL+F to find them):
- Change the SQL DB from sqlite to postgresql by replacing engine = create_engine('sqlite:///animalcatalog.db',connect_args={'check_same_thread': False}, poolclass=StaticPool, echo=True) with engine = create_engine('postgresql://catalog:catalog@localhost/catalog'). Do the same in the database_setup.py file where engine = create_engine('sqlite:///animalcatalog.db') needs to be replaced with engine = create_engine('postgresql://catalog:catalog@localhost/catalog').
- Remove the 2 lines app.debug = True and app.run(host='0.0.0.0', port=8000) and replace them with the single line app.run() in the __init__.py file.
Change the path for the client_secrets.json in the app with these 2 edits:
- CLIENT_ID = json.loads(open('client_secrets.json', 'r').read())['web']['client_id'] becomes CLIENT_ID = json.loads(open('/var/www/catalog/catalog/client_secrets.json', 'r').read())['web']['client_id']
- oauth_flow = flow_from_clientsecrets('client_secrets.json', scope='') becomes oauth_flow = flow_from_clientsecrets('/var/www/catalog/catalog/client_secrets.json', scope='')

Install virtual environment

The rest of the application is configured in a virtual environment. This article by geeksforgeeks explains some of the advantages.

To install the virtual environment, run these 2 commands:

$ sudo apt-get install python3-pip
$ sudo pip install virtualenv

Then, switch to the directory and activate it:

cd /var/www/catalog/catalog
virtualenv -p python3 venv3
$ sudo chown -R grader:grader venv3/
. venv3/bin/activate

Install Packages

Install all the packages that are imported in the python file for Python3 by running these commands:

pip3 install httplib2
pip3 install Flask
pip3 install requests
pip3 install --upgrade oauth2client
pip3 install sqlalchemy
sudo apt-get install libpq-dev
pip3 install psycopg2

Configure Virtual Host

Create a virtual host config file for the catalog and edit it via $ sudo nano /etc/apache2/sites-available/catalog.conf.. Change the content to:

<VirtualHost *:80>
    ServerName 52.34.208.247
    ServerAlias ec2-52-34-208-247.us-west-2.compute.amazonaws.com
    ServerAdmin [email protected]
    WSGIDaemonProcess catalog python-path=/var/www/catalog:/var/www/catalog/venv/lib/python2.7/site-packages
    WSGIProcessGroup catalog
    WSGIScriptAlias / /var/www/catalog/catalog.wsgi
    <Directory /var/www/catalog/catalog/>
        Order allow,deny
        Allow from all
    </Directory>
    Alias /static /var/www/catalog/catalog/static
    <Directory /var/www/catalog/catalog/static/>
        Order allow,deny
        Allow from all
    </Directory>
    ErrorLog ${APACHE_LOG_DIR}/error.log
    LogLevel warn
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

To enable the catalog run $ sudo a2ensite catalog and restart the apache2 with $sudo service apache2 reload.

Configure DB

The project also requires to not allow remote connections and create a new database user named catalog that has limited permissions to the catalog application database. To set this up, run the following commands:

$ sudo su - postgres
psql
CREATE USER catalog WITH PASSWORD 'catalog';
ALTER USER catalog CREATEDB;
CREATE DATABASE catalog WITH OWNER catalog;
\c catalog
REVOKE ALL ON SCHEMA public FROM public;
GRANT ALL ON SCHEMA public TO catalog;
\q
exit
. venv3/bin/activate
python /var/www/catalog/catalog/database_setup.py

Then, open the pg_hba.conf file with sudo nano /etc/postgresql/9.5/main/pg_hba.conf and make sure the the following permission are set:

local   all             postgres                                peer
local   all             all                                     peer
host    all             all             127.0.0.1/32            md5
host    all             all             ::1/128                 md5

Change Google Authentication

To make the OAUTH work with the webapplication, some last changes are needed to the Google Developer Console. Google does not allow to directly whitelist IP addresses, so either the host name has to be used or a service like xip.io.

In the Google console's applications tab "OAuth Consent Screen" the AWS domain has to be whitelisted by adding ec2-18-197-158-41.eu-central-1.compute.amazonaws.com to the list of authorized domains. Then, in the tab "Credentials" the "Authorized JavaScript origins" have to be modified to allow http://ec2-18-197-158-41.eu-central-1.compute.amazonaws.com and the "Authorized redirect URIs" need to include:

http://ec2-18-197-158-41.eu-central-1.compute.amazonaws.com/oauth2callback
http://ec2-18-197-158-41.eu-central-1.compute.amazonaws.com/classes/

Review Feedback

Based on the feedback of the reviewer, I re-run the package update/upgrade command to upgrade also kept back packages: $ sudo apt-get update && sudo apt-get dist-upgrade. Furthermore, I set up automatic updates according to this manual from libre-software:

Install unattended-upgrades package $ sudo apt install unattended-upgrades
Change $ sudo nano /etc/apt/apt.conf.d/50unattended-upgrades by uncommenting ${distro_id}:${distro_codename}-updates

Done!

Access the web application under http://ec2-18-197-158-41.eu-central-1.compute.amazonaws.com/. Thanks for testing it out!

Name		Name	Last commit message	Last commit date
Latest commit History 4 Commits
images		images
README.md		README.md

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Linux Server Configuration

Udacity Fullstack Nanodegree - Project 3

Introduction

What is this project about?

How is this document structured?

Get a server

Start an Ubuntu Server

SSH into the server

Secure the server

Update packages

Change SSH Port

Configure Uncomplicated Firewall

Give grader access

Create new user

Prepare deployment

Configuring Time Zone

Configuring Locale Setting

Install and configure Apache

Install PostgreSQL

Install git

Deploy the application

Clone Application

Update App Code

Install virtual environment

Install Packages

Configure Virtual Host

Configure DB

Change Google Authentication

Review Feedback

Done!

Special thanks to stueken who inspired iliketomatoes who in turn inspired kcalata. All of their detailed READMEs were very helpful.

About

Releases

Packages

nckre/Udacity-FullstackND-Project3-LinuxServer

Folders and files

Latest commit

History

Repository files navigation

Linux Server Configuration

Udacity Fullstack Nanodegree - Project 3

Introduction

What is this project about?

How is this document structured?

Get a server

Start an Ubuntu Server

SSH into the server

Secure the server

Update packages

Change SSH Port

Configure Uncomplicated Firewall

Give grader access

Create new user

Prepare deployment

Configuring Time Zone

Configuring Locale Setting

Install and configure Apache

Install PostgreSQL

Install git

Deploy the application

Clone Application

Update App Code

Install virtual environment

Install Packages

Configure Virtual Host

Configure DB

Change Google Authentication

Review Feedback

Done!

Special thanks to stueken who inspired iliketomatoes who in turn inspired kcalata. All of their detailed READMEs were very helpful.

About

Resources

Stars

Watchers

Forks

Releases

Packages 0

Packages