DEV Community: Okonkwo Valentine

How to Launch a Scalable WordPress Site on AWS Lightsail in Under 10 Minutes

Okonkwo Valentine — Sat, 02 Aug 2025 22:57:56 +0000

In today's fast-moving digital landscape, decision-makers are always looking for cost-effective, scalable, and secure ways to bring ideas to life—fast. Whether you’re a startup CEO launching your MVP, a CTO experimenting with content distribution, or a product owner needing a proof-of-concept blog or CMS, Amazon Lightsail offers an elegant, low-cost entry into cloud infrastructure without the usual DevOps overhead.

In this tutorial, I’ll show you how to deploy a fully functional WordPress website using AWS Lightsail in minutes—with zero prior cloud expertise required.

Why Use AWS Lightsail?
Before we dive into the steps, here’s why AWS Lightsail is worth considering:

a. Predictable pricing (starting from $3.50/month)

b. Pre-configured apps (e.g., WordPress, LAMP, Node.js)

c. One-click deployment

d. Easy scaling to EC2 if needed

e. Backed by AWS reliability & performance

Step-by-Step: Launch WordPress on Lightsail

a. Sign in to the AWS Console

b. Search for "Lightsail"

c. Click Create Instance

d. Choose Platform: Linux/Unix

e. Select App: WordPress

f. Choose an instance plan{e.g, $3.50/month}

g. Name your instance

h. Click Create Instance

*After 2-3 minutes, your instance will be ready

*Copy the Public IP address and paste it in a browser

*You will see your WordPress site live

h. Login using the default username/password provided in the instance settings.

*How to Login to WordPress:
In your browser, go to:

http://34.201.101.22//wp-admin

It will ask you for: a. username b. password

*How to Find the Default Password in AWS LightSail:

Go to AWS console
Click on your WordPress instance

Click the Connect using SSH button (this opens a terminal in your browser).

In the terminal, type the following command and press Enter: bash

*Use That to Log In:

*Conclusion: Launching a WordPress site on AWS Lightsail is more than just a technical exercise—it’s a strategic move. It demonstrates how cloud simplicity and affordability can empower small teams, early-stage startups, and even enterprise departments to move fast, test ideas, and deliver value without unnecessary overhead.

AWS Setup: EC2 + ALB + ASG for a Highly Available Web App

Okonkwo Valentine — Mon, 14 Jul 2025 15:18:10 +0000

Introduction

In today’s cloud-driven world, ensuring your web application is always available and resilient to failures is critical. This post walks you through the process of setting up a highly available and fault-tolerant web application on AWS using three core services: EC2 (Elastic Compute Cloud) for hosting, ALB (Application Load Balancer) for distributing traffic, and ASG (Auto Scaling Group) for automatic scaling and recovery. By the end of this setup, your app will be able to handle traffic efficiently across multiple Availability Zones — even if one instance fails.

Step 1:

Launch EC2 Instances (or Create a Launch Template) You can either manually launch 2 EC2 instances or create a Launch Template to use with an ASG.

AMI: Amazon Linux 2

Instance Type: t2.micro (Free tier)

Network: Default VPC

AZs: Choose different AZs (e.g., us-east-1a and us-east-1b)

Launch both instances and make sure they are running actively

Step 2: Install Apache Web Server
SSH into each instance and run:
bash
CopyEdit
sudo yum install httpd -y
sudo systemctl start httpd
sudo systemctl enable httpd
On WebServer1:bash
CopyEdit
echo "Welcome to Web Server 1 - $(hostname)" | sudo tee /var/www/html/index.html
On WebServer2:
bash
CopyEdit
echo "Welcome to Web Server 2 - $(hostname)" | sudo tee /var/www/html/index.html

Step 3: Create Target Group
• Target type: Instances
• Protocol: HTTP, Port: 80
• Health check path: /
• Register both instances.

Step 4: Create Application Load Balancer
• ALB type: Application Load Balancer
• Scheme: Internet-facing
• Listener: HTTP on port 80
• Subnets: Select at least 2 in different AZs
• Security Group: Allow HTTP (port 80)
Attach the previously created Target Group

Step 5: Test with curl from Git Bash
After setup, test the ALB using:
bash
CopyEdit
curl http://
Refresh multiple times — you should see responses from both WebServer1 and WebServer2 (round-robin behavior).

Conclusion

By combining EC2, ALB, and ASG, you've built a robust and scalable infrastructure that ensures your web application remains available even during instance failures or spikes in traffic. The use of multiple Availability Zones and automatic instance replacement through ASG highlights the power of cloud-native design for high availability. This setup not only improves fault tolerance but also prepares your application for real-world production environments on AWS.

Step-by-Step guide to Launching an EC2 instance on AWS( Amazon Web Services).

Okonkwo Valentine — Sat, 07 Jun 2025 12:10:28 +0000

Introduction

This project involves deploying an AWS EC2 Linux instance and establishing a connection to it using SSH. This includes selecting the appropriate Amazon Machine Image (AMI), configuring instance details, launching the instance, and ensuring proper security settings. Once the instance is running, the SSH client is used to connect to the instance securely, enabling remote access and management. Through this process, users gain practical experience in deploying cloud infrastructure and utilizing SSH for remote server access.

First, lets understand what an EC2 instance and SSH is all about:

An EC2 instance is a virtual server you can launch in the AWS cloud, allowing you to run applications and services. SSH (Secure Shell) is a secure protocol that allows you to remotely access and manage that EC2 instance. In essence, SSH provides a secure channel to connect to your EC2 instance, enabling you to interact with its operating system and manage it remotely.

Creating an EC2 Instance on a Linux Operating System and SSH involves the following step:

Step 1: Create an AWS Account

Go to the AWS portal page and Sign up for free tier account if you are a New User and once you are signed in successfully AWS portal page shows up that you are successfully logged in.

Step 2: Go to search bar on the AWS portal top, type EC2 and search then select the EC2 service

Step 3: Launch an EC2 instance on AWS portal option down right "option" and Click "Launch Instance" Button

Step 4: Choose an Instance Type: I selected the instance type based on my requirements as well. The instance type determines the computing power, memory and networking capacity of your instance and I named my instance "myfirstEC2" then select Amazon Linux 2023 AMI option.

Step 5: Choose types of computer options or instance type like "t2.micro" or "t3.nano". These are small free tier eligible instances types that defines the power of your computer.

Step 6: Create a Key Pair
I was prompted to create a key pair. if you do not have an existing key pair, create a new one and name it "my-ec2-key" then save it and I used ".pem" as the file format.

Step 7: Leave VPC and subnet as default settings or customize them according to your needs. Ensure "Auto assign Public IP" is enabled then create a new security group with one rule type: SSH {port 22} source or use an existing one. A security group acts as a virtual firewall for your instance, controlling inbound and outbound traffic. Click " Review and Launch" after configuring the security group.

Step 8: "Review and Launch"
Next in the process, I reviewed all the configurations I made for my instance and saw that everything looked good, so I clicked "Launch Instance" to proceed.

I waited for instance to Launch, it may take a few minutes for your instance to launch. Once it is ready, you will see it listed on the EC2 Dashboard.

Connecting the using SSH: Now, open your terminal or SSH client. Use the following command to connect to your instance

Conclusion: You have now successfully created an EC2 instance on Linux operating system then launching the instance to be successful.

Assignment: Understanding Servers and Cloud Computing

Okonkwo Valentine — Wed, 28 May 2025 17:06:19 +0000

Introduction

This document explores the foundational concepts of Servers and Cloud Computing. It delves into the distinctions between hardware and software server environments, outlines various server types, and clarifies different cloud deployment models. Furthermore, it provides a comparative analysis of key cloud service models (IaaS, PaaS, SaaS) and applies this knowledge to a practical business scenario, recommending suitable cloud infrastructure and AWS services.

Part A

Difference between hardware and software servers ?

A hardware server is a physical computer that runs server software, while a software server is the software itself that enables a computer to act as a server.

Name and example of 3 types of servers ?

a. Web servers e.g (Apache, Nginx & IIS)

b. Database servers e.g (mySQL, Oracle & postgreSQL)

c. File servers e.g They are commonly used in office networks.

Cloud Deployment Models
- private cloud
- public cloud
- hybrid cloud
compare iaaS, paaS, saaS with example
Ans- IaaS, PaaS, and SaaS represent different levels of cloud computing services, each offering a varying degree of control and responsibility. IaaS provides the foundational infrastructure, PaaS offers a platform for development and deployment, and SaaS delivers pre-built software applications
examples of iaaS - (AWS) EC2 which allows you create and manage virtual servers on demand.
paaS - Heroku which provides a platform for deploying web applications without managing servers.
saaS - Google Workspace( including Gmail, Google Docs etc. ) which provides cloud-based email, document creation, and collaboration tools.

Part B True or False

SaaS let users manage everything - False
On-premises can scale easily- False
DNS converts IP to domain name - False
Cloud requires upfront hardware payment- False

Part C

You’re starting a business. Which model do you use and why ? Choose AWS services for storage, backend, and database.

Ans- For a new business, a serverless-first architecture using AWS services is highly recommended. This model leverages AWS's managed services to handle backend infrastructure, enabling you to focus on building and scaling your application.

Here's a breakdown of why and which AWS services to consider:

Why Serverless-First:

a. Cost-Effectiveness:  You only pay for resources used, reducing operational costs and upfront investments.   

b. Scalability:  Easily scale up or down based on demand without managing infrastructure

c. Reduced Management Overhead:  AWS handles infrastructure management, simplifying operations and allowing you to focus on the core business   

d. Increased Agility:  Easier to deploy and update applications, fostering innovation and faster time-to-market.

AWS Services for Storage, Backend, and Database:

Storage:

Amazon S3: Ideal for storing unstructured data, such as files, documents, images, and videos. Offers high durability, security, and scalability, according to Aligned Technology Group.    Backend (Compute):
Amazon API Gateway: Facilitates API management, allowing you to control access, monitor requests, and manage API versions.
AWS Lambda: A serverless compute service that executes code without provisioning or managing servers. This is a great option for backend logic and event-driven applications.

Database:

Amazon DynamoDB: A serverless NoSQL database, perfect for fast, scalable applications where data access patterns are highly flexible. DynamoDB is a fully managed service, meaning you don't have to worry about managing database servers.  
Amazon RDS (Relational Database Service): If you require a relational database, RDS makes it easy to set up, operate, and scale a database in the cloud.

Benefits of this Approach:

a. Reduced Infrastructure Costs:  You only pay for what you use, making it cost-effective for startups and businesses of all sizes.   

b. Enhanced Scalability:  Easily adapt to changing business needs without the burden of managing infrastructure.   

c. Increased Agility:  Deploy and update your application more rapidly, allowing for faster innovation and time-to-market.

d. Focus on Core Business:  AWS handles the infrastructure, allowing you to focus on building and scaling your application.

cloud computing

Okonkwo Valentine — Tue, 20 May 2025 13:55:40 +0000