DEV Community

Cover image for LAMP Stack (WEB STACK) Implementation in AWS
Uwadone Joshua
Uwadone Joshua

Posted on

LAMP Stack (WEB STACK) Implementation in AWS

#webdev #aws #devops #webserver

WEB STACK IMPLEMENTATION (LAMP STACK) IN AWS

Introduction:

The LAMP stack is a popular group of open-source software that consists of four main components: Linux, Apache, MySQL, and PHP (or sometimes Perl or Python). It is typically installed together in order to enable a server to host dynamic websites and web apps written in PHP.
This term is an acronym which represents the Linux operating system with the Apache web server.
The site data is stored in a MySQL database, and dynamic content is processed by PHP. This documentation outlines the setup, configuration, and usage of the LAMP stack.

Linux

Linux is the foundational layer of the LAMP stack, providing the operating system on which all the other components run. As an open-source, Unix-like operating system,
Linux offers a highly customizable and secure platform that powers most of the world's servers.
Its compatibility with other open-source software and widespread community support make it the preferred choice for web hosting environments.
Popular Linux distributions used in LAMP stacks include Ubuntu, CentOS, and Debian.

Apache

Apache is the web server software that handles serving web pages to users.
It processes HTTP requests from client browsers and delivers content such as HTML pages, images, and scripts.
Apache also supports advanced features including virtual hosting, secure connections (SSL/TLS), and URL rewriting.
Key Features of Apache:
Modular Design: Apache allows administrators to enable or disable different modules, such as SSL for encryption or mod_rewrite for URL manipulation.
Virtual Hosting: Apache can host multiple websites on a single server, each with its own domain name and directory.
SSL/TLS Support: Apache can secure connections between the server and clients using SSL (Secure Sockets Layer) and TLS (Transport Layer Security).
Cross-Platform: Although it runs best on Linux, Apache is also compatible with other operating systems like Windows and macOS.

MySQL (or MariaDB)

MySQL is a relational database management system (RDBMS) used for storing and managing structured data in web applications.
Its client-server architecture supports multiple clients performing operations such as data retrieval, manipulation, and deletion.
MariaDB, a fork of MySQL, provides additional features and performance enhancements while maintaining compatibility with MySQL.

PHP (or Perl/Python)

PHP is a server-side scripting language designed to create dynamic web content.
Embedded within HTML code, PHP executes on the web server to generate content dynamically before sending it to the client.
It interacts with databases, processes forms, and performs various tasks necessary for developing interactive web applications.
Alternative scripting languages like Perl and Python can also be used in place of PHP, depending on the specific needs of the application.

Use Cases for LAMP Stack

Content Management Systems (CMS): Platforms like WordPress, Drupal, and Joomla run on the LAMP stack.
E-commerce Websites: Many online stores use the LAMP stack to manage dynamic content, handle payments, and process user data.
Web Applications: From social networking sites to business applications, the LAMP stack provides the necessary infrastructure to support complex web-based platforms.
Custom Web Development: Developers can use the LAMP stack for custom web applications that require robust back-end support with PHP and MySQL, such as blogs, forums, or project management tools.

Step 0: Prerequisites

1. Launched an Ubuntu EC2 Instance named “Lamp_Stack_Server” with AMI of 24.04 LTS (HVM) in the us-west-2 region using the AWS console.

Launch Instance

2. Gave it the instance type of t2.micro which is within the free-tier. Created SSH key pair named lamp_stack to access the instance on port 22. The default VPC and Subnet were used for the networking configuration.

Set Instance Type

3. The security group was configured with the following inbound rules:

  • Allow traffic on port 22 (SSH) with source from any IP address. This is opened by default.
  • Allow traffic on port 443 (HTTPS) with source from anywhere on the internet.
  • Allow traffic on port 80 (HTTP) with source from anywhere on the internet. And will leave the storage at default; 8gb gp3 volume storage. Then we hit the launch instance button.

Security Rules

4. First, we need to move the keypair file from the download folder into the .ssh folder;
cp ~/Downloads/lamp_stack.pem ~/.ssh/

The private ssh key that got downloaded has now been moved, permission was changed for the private key file and then used to connect to the instance by running the following commands;

chmod 400 ~/.ssh/lamp_stack.pem
Enter fullscreen mode Exit fullscreen mode 
ssh -i ~/.ssh/lamp_stack.pem [email protected]
Enter fullscreen mode Exit fullscreen mode

Where username=ubuntu and public ip address=35.93.146.45

Connect to instance

Step 1 - Install Apache and Update the Firewall

1. Update and upgrade list of packages in package manager

sudo apt update


![Update Packages](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/0zxegjkabpl6ti9ixmn6.png)

sudo apt upgrade -y
Enter fullscreen mode Exit fullscreen mode

Upgrade Packages

2. Run apache2 package installation

sudo apt install apache2 -y
Enter fullscreen mode Exit fullscreen mode

Install Apache

3. Enable and verify that apache is running on as a service on the OS.

sudo systemctl enable apache2
sudo systemctl status apache2
Enter fullscreen mode Exit fullscreen mode

sudo systemctl enable apache2: Configures Apache to start on boot (so it survives a restart).

If it green and running, then apache2 is correctly installed

Apache Status

4. The server is running and can be accessed locally in the ubuntu shell by running the command below:

curl http://localhost:80
OR
curl http://127.0.0.1:80
Enter fullscreen mode Exit fullscreen mode

Curl Local Host

5. Test with the public IP address if the Apache HTTP server can respond to requests from the internet using the url on a browser.

http://35.93.146.45:80
Enter fullscreen mode Exit fullscreen mode

Apache Default Page

This shows that the web server is correctly installed and it is accessible through the firewall.

6. Another way to retrieve the public IP address other than check the aws console

TOKEN=$(curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600")
curl -H "X-aws-ec2-metadata-token: $TOKEN" -s http://169.254.169.254/latest/meta-data/public-ipv4

![Obtain IP via the CLI](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/zrhwd5jhuq74uf7qq21t.png)![imds option](./images/imds-option.png)
Enter fullscreen mode Exit fullscreen mode

Or enable IMDSv1 in your instance settings:
Go to EC2 Console → Instances → Select your instance.
Actions → Instance Settings → Modify Metadata Options.
Set Metadata version to V1 and V2.
Change the IMDSv2 from Required to Optional.

The command was run,and the public IP address was displayed. Thing is AWS now defaults to IMDSv2 (Instance Metadata Service Version 2), which requires token.

TOKEN=$(curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600")
curl -H "X-aws-ec2-metadata-token: $TOKEN" -s http://169.254.169.254/latest/meta-data/public-ipv4
Enter fullscreen mode Exit fullscreen mode

Step 2 - Install MySQL

1. Install a relational database (RDB)

MySQL was installed in this project. It is a popular relational database management system used within PHP environments. We use MySQl as a relational database to store and manage data on our website.

sudo apt install mysql-server
Enter fullscreen mode Exit fullscreen mode

Install MySQL

When prompted, install was confirmed by typing y and then Enter.

2. Enable and verify that mysql is running with the commands below

sudo systemctl enable --now mysql
sudo systemctl status mysql
Enter fullscreen mode Exit fullscreen mode

NB: sudo systemctl enable --now mysql: --now starts MySQL immediately, and enable ensures it runs at boot.

MySQL Status

3. Log in to mysql console

sudo mysql
Enter fullscreen mode Exit fullscreen mode

This connects to the MySQL server as the administrative database user root inferred by the use of sudo when running the command.

4. Set a password for root user using mysql_native_password as default authentication method.

Here, the user's password was defined as "Admin007$"

ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'Admin007$';
Enter fullscreen mode Exit fullscreen mode

User Password/MyQL login
Exit the MySQL shell

exit
Enter fullscreen mode Exit fullscreen mode

5. Run an Interactive script to secure MySQL

The security script comes pre-installed with mysql. This script removes some insecure settings and lock down access to the database system.

NB: The command below launches an interactive script that:
Sets password validation rules (if chosen).

Removes test users and databases.

Disables root login remotely (optional).

Reloads privilege tables.

sudo mysql_secure_installation
Enter fullscreen mode Exit fullscreen mode

Iteractive Change

We use the sudo mysql_secure_installation command to remove insecure default settings and enable protection for the database.

Regardless of whether the VALIDATION PASSWORD PLUGIN is set up, the server will ask to select and confirm a password for MySQL root user.

6. After changing root user password, log in to MySQL console.

A command prompt for password was noticed after running the command below.

sudo mysql -p
Enter fullscreen mode Exit fullscreen mode

Password Change

Exit MySQL shell

exit
Enter fullscreen mode Exit fullscreen mode

Step 3 - Install PHP

1. Install php
Apache is installed to serve the content and MySQL is installed to store and manage data.
PHP is the component of the set-up that processes code to display dynamic content to the end user.

The following were installed:

  • php: The scripting language.
  • php-mysql: PHP module that allows PHP to communicate with MySQL-based databases.
  • libapache2-mod-php: Module to run PHP with Apache and enable Apache to handle PHP files. 
sudo apt install php libapache2-mod-php php-mysql
Enter fullscreen mode Exit fullscreen mode

Install PHP

Confirm the PHP version

php -v
Enter fullscreen mode Exit fullscreen mode

Confirm php version

At this point, the LAMP stack is completely installed and fully operational.

To test the setup with a PHP script, it's best to set up a proper Apache Virtual Host to hold the website files and folders. Virtual host allows to have multiple websites located on a single machine and it won't be noticed by the website users.

Step 4 - Create a virtual host for the website using Apache

1. The default directory serving the apache default page is /var/www/html. Create your document directory next to the default one.

Apache webserver serves a website by way of server blocks inside its /var/www/ directory, and it can support multiple of this server blocks to host other websites.

Here we create a new directory called ‘projectlamp’ inside the /var/www/ directory using "mkdir" command

sudo mkdir /var/www/projectlamp
Enter fullscreen mode Exit fullscreen mode

Assign the directory ownership with $USER environment variable which references the current system user, i.e we change the permissions of the projectlamp directory to the current user system..

sudo chown -R $USER:$USER /var/www/projectlamp
Enter fullscreen mode Exit fullscreen mode

NB: This command changes ownership to your user (so you can easily modify files).

MKDIR CHOWN

2. __ The projectlamp directory represents the directory which will contain files related to our website as it represents a new server block on the apache webserver. In order to spin up this server block we need to configure it by creating a .conf file.

Create and open a new configuration file in apache’s “sites-available” directory using vim.__

sudo vim /etc/apache2/sites-available/projectlamp.conf
Enter fullscreen mode Exit fullscreen mode

The following represents the configuration needed to spin up the server block. Copy and paste in the bare-bones configuration below into the editor.:

<VirtualHost *:80>
  ServerName projectlamp
  ServerAlias www.projectlamp
  ServerAdmin webmaster@localhost
  DocumentRoot /var/www/projectlamp
  ErrorLog ${APACHE_LOG_DIR}/error.log
  CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>
Enter fullscreen mode Exit fullscreen mode

Virtual Host in VI

3. Show the new file in sites-available

sudo ls /etc/apache2/sites-available
Enter fullscreen mode Exit fullscreen mode 
Output:
000-default.conf default-ssl.conf projectlamp.conf
Enter fullscreen mode Exit fullscreen mode

Projectlamp config file

With the VirtualHost configuration, Apache will serve projectlamp using /var/www/projectlamp as its web root directory.

4. Enable the new virtual host

sudo a2ensite projectlamp
Enter fullscreen mode Exit fullscreen mode

So, we run sudo a2ensite projectlamp to activate the server block.
NB: Activates your config by creating a symbolic link in sites-enabled.

Enable virtual host

5. Disable apache’s default website.

This is because Apache’s default configuration will overwrite the virtual host if not disabled. This is required if a custom domain is not being used.

sudo a2dissite 000-default
Enter fullscreen mode Exit fullscreen mode

We run ‘sudo a2dissite 000-default’ to deactivate the default webserver block that comes with apache on default.
NB: Prevents Apache from using the default config, this is important to avoid conflicts.

Disable Apache default

6. Ensure the configuration does not contain syntax error

The command below was used:

sudo apache2ctl configtest
Enter fullscreen mode Exit fullscreen mode

Check syntax error

7. Reload apache for changes to take effect.

sudo systemctl reload apache2
Enter fullscreen mode Exit fullscreen mode
  1. The new website is now active but the web root /var/www/projectlamp is still empty. Create an index.html file in this location, so as to test the virtual host work as expected. 
sudo echo 'Hello LAMP from hostname' $(curl -s http://169.254.169.254/latest/meta-data/public-hostname) 'with public IP' $(curl -s http://169.254.169.254/latest/meta-data/public-ipv4) > /var/www/projectlamp/index.html
Enter fullscreen mode Exit fullscreen mode

Or

sudo bash -c "echo 'Hello LAMP from hostname' \$(curl -H \"X-aws-ec2-metadata-token: $TOKEN\" -s http://169.254.169.254/latest/meta-data/public-hostname) 'with public IP' \$(curl -H \"X-aws-ec2-metadata-token: $TOKEN\" -s http://169.254.169.254/latest/meta-data/public-ipv4) > /var/www/projectlamp/index.html"
Enter fullscreen mode Exit fullscreen mode

Root dir content

  1. Open the website on a browser using the public IP address.

http://35.93.146.45:80

URL public IP

10. Open the website with public dns name (port is optional)

http://<public-DNS-name>:80
Enter fullscreen mode Exit fullscreen mode

URL public DNS

This file can be left in place as a temporary landing page for the application until an index.php file is set up to replace it. Once this is done, the index.html file should be renamed or removed from the document root as it will take precedence over index.php file by default.

Step 5 - Enable PHP on the website

With the default DirectoryIndex setting on Apache, index.html file will always take precedence over index.php file. This is useful for setting up maintenance page in PHP applications, by creating a temporary index.html file containing an informative message for visitors. The index.html then becomes the landing page for the application. Once maintenance is over, the index.html is renamed or removed from the document root bringing back the regular application page.
If the behaviour needs to be changed, /etc/apache2/mods-enabled/dir.conf file should be edited and the order in which the index.php file is listed within the DirectoryIndex directive should be changed.

NB: By default, the webserver has a preference for serving an index.html file based on the order of precedence by default in the DirectoryIndex settings of Apache.
To serve an index.php containing the server-side code, you’ll need to edit the /etc/apache2/mods-enabled/dir.conf file and change the order in which the index.php file is listed within the DirectoryIndex.

1. Open the dir.conf file with vim to change the behaviour

sudo vim /etc/apache2/mods-enabled/dir.conf
Enter fullscreen mode Exit fullscreen mode 
<IfModule mod_dir.c>
  # Change this:
  # DirectoryIndex index.html index.cgi index.pl index.php index.xhtml index.htm
  # To this:
  DirectoryIndex index.php index.html index.cgi index.pl index.xhtml index.htm
</IfModule>
Enter fullscreen mode Exit fullscreen mode

NB: We want to prioritize index.php over index.html

Change file list order

2. Reload Apache

Apache is reloaded so the changes takes effect.

sudo systemctl reload apache2
Enter fullscreen mode Exit fullscreen mode

3. Create a php test script to confirm that Apache is able to handle and process requests for PHP files.

A new index.php file was created inside the custom web root folder.

vim /var/www/projectlamp/index.php
Enter fullscreen mode Exit fullscreen mode

Add the text below in the index.php file

<?php
phpinfo();

NB: phpinfo() shows your PHP environment info in browsers, this is useful for confirming PHP is working correctly.

Php Text

  1. Now refresh the page

Page Reload

This page provides information about the server from the perspective of PHP. It is useful for debugging and to ensure the settings are being applied correctly.

After checking the relevant information about the server through this page, It’s best to remove the file created as it contains sensitive information about the PHP environment and the ubuntu server. It can always be recreated if the information is needed later.

sudo rm /var/www/projectlamp/index.php

Conclusion:

The LAMP stack provides a robust and flexible platform for developing and deploying web applications. By following the guidelines outlined in this documentation, It was possible to set up, configure, and maintain a LAMP environment effectively, enabling the creation of powerful and scalable web solutions.

Top comments (0)