DEV Community: Oluwatobi

How to Deploy a Static Website with S3 and CloudFront on AWS

Oluwatobi — Tue, 27 May 2025 18:25:41 +0000

Want to host a fast, secure, and globally distributed website with no backend server?

In this hands-on guide, I’ll walk you through how to host a static website using Amazon S3 and CloudFront — perfect for portfolios, documentation, or product landing pages.

What You’ll Need

✅ An AWS Account (free tier works)
✅ A static website (HTML, CSS, JS files)
✅ Optional: Custom domain + SSL

Step-by-Step Guide

🔹 Step 1: Create an S3 Bucket

Go to S3 in AWS Console.

Click "Create Bucket"

Name it exactly as your domain name (e.g. mywebsite.com)

Uncheck Block all public access ✅ (you’ll change permissions later)

Create Bucket > click on the created bucket >

Enable static website hosting:
Under "Properties" > Static Website Hosting

Select: Enable

Enter your index.html and error.html file names

🔹 Step 2: Upload Your Website Files

Upload your index.html, styles.css, and other static files into the bucket.

🔹 Step 3: Set Bucket Policy for Public Read

Go to Permissions > Bucket Policy

and paste this (update your bucket name):

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "PublicReadGetObject",
      "Effect": "Allow",
      "Principal": "*",
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::your-bucket-name/*"
    }
  ]
}

🔹 Step 4: Set Up CloudFront

Go to CloudFront > Create Distribution

Under Origin domain, choose your S3 bucket

Set Viewer Protocol Policy to Redirect HTTP to HTTPS

Enable Custom Error Responses (optional)
Leave other defaults or fine-tune caching rules

🔹 Step 5: Connect a Custom Domain (Optional)
If you have a domain (from Route 53 or elsewhere):

Add an alternate domain name (CNAME) to CloudFront

Use AWS Certificate Manager (ACM) to create an SSL cert

Update your DNS settings to point to the CloudFront distribution

💡 Bonus Tips
✅ Enable versioning in S3 for rollbacks

✅ Use CloudFront invalidation to force-refresh cache

✅ Add security headers with Lambda@Edge (advanced)

🎉 Done! Your Static Site is Live on AWS
You now have a fast, global, scalable site hosted with S3 and accelerated by CloudFront.

💰 How to Use S3 Lifecycle Policies to Save Money and Stay Organized on AWS"

Oluwatobi — Mon, 05 May 2025 19:10:26 +0000

If you're storing data on AWS S3 and not using lifecycle policies, you're probably overspending.

In this guide, I’ll walk you through how to set up S3 Lifecycle Rules to automate storage transitions, save money, and keep your data clean.

🛠️ Why S3 Lifecycle Policies Matter

S3 is one of AWS’s most used services—and for good reason. It’s durable, flexible, and easy to use.

But here’s the catch:

If you don’t actively manage your storage, your costs can quietly stack up.

Lifecycle policies help you automatically:

✅ Move files to cheaper storage classes
✅ Delete unnecessary files on schedule

📦 S3 Storage Class Cheatsheet

Storage Class	Use Case	Cost
Standard	Frequent access	💸 High
Intelligent-Tiering	Dynamic access patterns	⚖️ Balanced
One Zone-IA	Rare access, lower durability	💵 Lower
Glacier	Archival, infrequent access	🧊 Very low
Glacier Deep Archive	Long-term cold storage	❄️ Lowest

🧪 Use Case: Archiving Logs Automatically

Imagine you store logs that are only useful for 30 days. After that, you want to:

Archive them to Glacier
Delete them after 6 months

Here’s how you can do that 👇

⚙️ Step-by-Step: Setting Up an S3 Lifecycle Rule

🔹 1. Open the AWS S3 Console

Go to: S3 > Select Your Bucket > Management > Lifecycle Rules > Create Rule

🔹 2. Name Your Rule

Example: ArchiveLogsToGlacier

🔹 3. Choose Filter (Optional)

Apply the rule to:

All objects
A prefix (e.g., logs/)
Or tagged objects Tags are great for fine-grained control. Example:

{
  "project": "analytics"
}

🔹 4. Set Transitions

Transition to GLACIER after 30 days

🔹 5. Set Expiration

Delete objects after 180 days

🔹 6. Review & Create

Done! Now AWS handles the cleanup for you.

🧠 Best Practices

✅ Use object tagging to separate lifecycles per project
✅ Combine with Intelligent-Tiering when access patterns are unpredictable
✅ Monitor with AWS CloudTrail or CloudWatch for visibility

🧾 Example JSON Rule (for automation)
If you're using Terraform, here's a snippet:

lifecycle_rule {
  id      = "archive_logs"
  enabled = true

  prefix = "logs/"

  transition {
    days          = 30
    storage_class = "GLACIER"
  }

  expiration {
    days = 180
  }
}

🔚 Conclusion

S3 Lifecycle Policies are simple yet powerful. Whether you're managing logs, backups, or raw data dumps, they help:

Cut costs
Maintain hygiene
Automate boring tasks

💬 Your Turn!

Are you using S3 lifecycle rules yet?
Or planning to? What use cases do you have in mind?

Let me know in the comments 👇

AWS Virtual Private Cloud

Oluwatobi — Sun, 01 Sep 2024 20:53:07 +0000

Project Description:

We'll explore the core concept of Amazon Web Service (AWS), focusing specifically on virtual Private Clouds (VPCs)

Subnets
Gateways
Routing tables We'll navigate the AWS management console to deploy and manage these critical components effectively.

Project Goals:

Setting up and configuring VPC, Subnets, internet gateway, NAT gateway
Enable internet connectivity securely within VPC
Implement outbound internet access through the NAT gateway.

Step 1: Setting up a Virtual Private Cloud (VPC)

Navigate to the search bar and enter VPC

Navigate to the "Create VPC" option and click on it

Select the "VPC only" option, specify the IPv4 CIDR block, and proceed by clicking on the "Create VPC" button.

Note: If you encounter an error message stating that the CIDR block must be between '/16 and /28' when creating a VPC, it indicates that your provided CIDR block falls outside of this recommended range.

VPC created

Step 2: Configuring Subnets within the VPC

Navigate to the "Subnets" option located on the left sidebar.
Proceed to click on the "Create Subnet" button.

Select the ID of the VPC that you created in the previous step

Enter the subnet name, and specify the IPv4 CIDR for the subnet.
choose the availability zone
Specify the IPv4 CIDR for the subnet
To create another subnet, Click on the "Add subnet" button.

Repeat the same steps for the second subnet
Ensuring to specify the subnet name, choose the availability zone, and provide the IPV4 CIDR

Your subnets is being created

Step 3: Creating Internet Gateway

Navigate to the "Internet Gateway"
Click on the "Create Internet Gateway"

Specify the name of Internet Gateway
Click on the "Creating Internet Gateway"

Your internet gateway is being successfully created.

Now, you will notice that it is currently detached, indicating that it is not associated with any VPC. To enable internet connectivity, you must attach the Internet Gateway to the VPC you have previously created.

Now, attach it to the VPC

Successfully attached

Step 4: Creating Route Tables

Let's come to the next part which is enabling internet connectivity with the internet Gateway by setting up routing tables

Proceed to the " Route Tables"
Click on the "Create route table

Enter the name of the route table and select the VPC you previously created
Create a route table

Click on "Subnet association" followed by "edit subnet associations" to associate the subnet with the route table

Choose the public subnet and click on Save association.

Navigate to "Routes" and then click on "Edit routes"

Click on add route
Select "Destination" as "0.0.0.0/0", indicating that every IPV4 address can access this subnet
"Target Field", Choose "Internet Gateway" and then select the Internet Gateway you created. finally, save the changes.

Step 5: Creating NAT Gateway

Navigate to the "NAT Gateways" then click on "Create NAT Gateway"

Choose the Private subnet
Select the connectivity type as private
Create NAT Gateway

Your NAT Gateway is being created successfully

Select your NAT Gateway.
Navigate to the " Details tab
Locate the subnet ID and click on it

Navigate to the "Route Table" section.
Then click on the "route table ID"

Proceed to the "Routes" section, then click on "Edit routes"

Then click on "Add routes"
Select "Destination" as "0.0.0.0/0"
In the "Target" field, choose the "NAT Gateway you created.
Finally, save the changes

On the subnet association section, click on the edit subnet association

Choose the private subnet and click on "Save associations"

The subnet has been successfully attached to the route table

Aws-S3-Bucket-Policy-Exploration

Oluwatobi — Sun, 04 Aug 2024 20:08:41 +0000

Project Description:

This project will guide you through creating a simple S3 bucket, defining a policy to manage access permissions, creating IAM Users and Groups, and assigning roles to each group.

Project Task:

Create an S3 Bucket
Understanding S3 Bucket Resource Base Policies
Create IAM users and Groups
Policy Configuration

Step 1: Create an S3 bucket

Navigate to the S3 service

Click the "Create bucket" button

Follow the prompts to configure your new S3 bucket ( maintain the default settings)

You might get this prompt, S3 naming convention is unique (You can't have two buckets with the same name in the whole of AWS infrastructure)
Add some extra characters or texts

Step 2: Understanding S3 Bucket Policies [How Amazon S3 works with IAM]

Scenario: As the cloud Architect, you're to

Create IAM users, and assign them to different groups

Group 1 - Developers [Users - Gift, grace]
Group 2 - Auditors [Ali, Josh]
Group 3 - Operations [ Samuel, Lovet]

Assign different roles (policies) to each group

Groups	Roles
Developers	EC2
Auditors	Billing and cost Management
Operation	Networking

Each Group has a lead, assign Resource-based policies within Amazon S3 only to the lead of each group

2.1 Creating groups and assigning permissions

Navigate to IAM

Select User groups

Create groups

Apply the same Steps to create the other groups

### 2.2 Creating and Adding Users

Apply the same Steps to create the Users you want

2.3 Assign Resource-based policies within Amazon S3 only to the lead of each group

Assuming the leads are

Auditors - Ali

Developers - Grace

Operations - Samuel

Navigate to the bucket you created

Select Permission

Edit Bucket Policy

Copy this code

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AddPublicReadCannedAcl",
            "Effect": "Allow",
            "Principal": {
                "AWS": [
                    "arn:aws:iam::471112799800:user/Ali",
                    "arn:aws:iam::471112799800:user/Samuel",
                    "arn:aws:iam::471112799800:user/grace"
                ]
            },
            "Action": [
                "s3:PutObject",
                "s3:PutObjectAcl"
            ],
            "Resource": "arn:aws:s3:::bucketttesting/*",
            "Condition": {
                "StringEquals": {
                    "s3:x-amz-acl": "public-read"
                }
            }
        }
    ]
}

Edit the principal, Copy the ARN URL of the users

Edit the Resource, Copy the bucket ARN
You can edit the action if you want

Save Changes

Alternatively

Use the policy generator

Select S3 Bucket policy

Select Allow

Select any action, you can select as many as you like

Copy the bucket ARN

Select Generate Policy

How to build and Deploy an E-Commerce Platform with Git-Linux-and-AWS

Oluwatobi — Wed, 31 Jul 2024 18:16:40 +0000

Project Description:

To develop an e-commerce website for a new online marketplace name "Agate Interior". This platform will feature product listings, a shopping cart, and user authentication.

Task:

To utilize Git for version control, develop the platform in a Linux environment, and deploy it on an AWS EC2 instance.
Continous integration and development workflow
Developing New features and fixes
Version Control with Git
Pull Requests and Merging to ain branch
Deploying Updates to the Production Server
Testing the new changes

Step 1:

Initialize Git Repository

Create a new Repository

Copy SSH/HTTP (depending on the one you use best)

Clone the Repo
git clone "Paste the URL"
Confirm it has been successfully downloaded into your local Repo

## Step 2:

Obtain and Prepare the E-Commerce Website Template

Instead of developing the website from scratch, use a pre-existing e-commerce website template

Download A website template from (https://www.tooplate.com/) or any website template hub you know

Extract the Downloaded template into your project Directory that you've created
Customize the template if you have a basic web development skill. (I Tailored mine to Agate Interior)

## Step 3:

Stage and Commit the Template to Git

Run ls to confirm the directory
git add "Directory_name" to stage the codes

Run git status to see if it's successfully staged

Run git commit -m "your message" to commit your code

git push / git push -u origin main to push your code to your remote Repo

Go to your Github to confirm the changes

## Step 4:

AWS Deployment

To deploy, you'll start by setting up an Amazon EC2 instance

Launch An EC2 Instance Using an Amazon Linux AMI
Remember to download a key pair

Connect to the to your local Repo using SSH
Copy the URL

You have successfully launched an EC2

## Step 5:

Connect and Clone the repository on the Linux Server

You need to clone the GitHub repository to your AWS EC2 instance. This process involves authenticating with GitHub using SSH

Open your Local Server
Paste the URL copied from your EC2 to connect your local server to the remote server

Run ssh-keygen to generate an SSH keypair
Press enter to use the default file directory and passphrase

Run cat /home/ec2-user/.ssh/id_rsa.pub (copy the content)

Navigate to your Repository in GitHub Console, click on settings

Navigate to SSH and GPG key, create a new SSH key

Paste the Copied content, and add the SSH key

Install git on your EC2 server if you have it installed

To check if it is installed or not

Run which git

To install, run sudo yum install git

Clone the Repository

Navigate back to Repo and copy the SSH URL

Clone Repo

## Step 6:

Install a Web Server on EC2

Apache HTTP Scerver

Installing it on Linux EC2 server allows you to host "Agate Interior"

Install the Apache web server on the EC2 instance.

sudo yum update -y
sudo yum install httpd -y
sudo systemctl start httpd
sudo systemctl enable httpd

Configure httpd for the website

sudo rm -rf /var/www/html/*
sudo cp -r ~Agate_interior/* /var/www/html/

Reload httpd

sudo systemctl reload httpd

Step 7:

Success Website from browser

Open a web browser and access the public IP of your EC2 instance to view the deployed website

## Step 8:

Continuous Integration and Deployment Workflow

Developing New Features and fixes
git checkout -b Development to create a new branch

Make your New development

Stage your Edit

git add "index.html"
git commit -m "your message"
git push

Go to your GitHub

Git pull

Step 8:

Deploying Updates to the Production Server

Pull the latest changes on the Server

Follow and study the code

Code Updated

Before

After

EC2-and-S3-integration-for-Zappy-E-bank

Oluwatobi — Tue, 30 Jul 2024 13:24:10 +0000

Mini Project: EC2-and-S3-integration-for-zappy-e-bank

Project Description:

Zappy E-bank plans to deploy its application on AWS ECS, with S3 buckets serving as the backbone for storage solutions, including customer data, transaction logs, and analytical data. The integration of EC2 and S3, facilitated by a reversed proxy setup, aims to provide a seamless experience for managing and accessing diverse resources under a unified access point.

Project Task:

EC2: Host the core application, enabling scalable computing capacity to meet growing customer demands.

S3: Offers secure, scalable objects strong for vast amounts of data, ensuring that Zappy E-bank can serve its customers efficiently and reliably.

Tips

A reverse Proxy will be configured on the EC2 instance, directing requests to the appropriate destination.

This also explains how to launch an EC2 instance

Step 1:

Step 2:

Launching An Instance

Search for EC2

Click on Launch Instance

Insert your project Name

Select an Operating system to run (I'll be using the Ubuntu instance)

Select Instance Type

You can decide to generate a key pair if you want to connect to a local server, but I won't be needing it here

Select Network Settings

Proceed without key pair

Connect to instance

You have successfully created an instance

Step 3:

Assigning a Static IP (Elastic IP)

Associating an Elastic IP address with your EC2 instance ensures it retains the same public IP address across reboots.

In the EC2 console navigation, select elastic IP and click on allocate elastic

Follow the highlighted part

Click on Associate

Step 4:

Creating S3 Bucket

Search S3 and click

Create a new bucket and give it a name of your choice

Create a new object inside the bucket. You should upload an index.html file containing

On your computer, create an index.html file with the content "Welcome to Amazon

Upload the index.html on S3 bucket as shown in the image below;

Step 5:

Configuring S3 Bucket for Web Hosting

Click on your bucket name

Click on the properties tab and scroll down

Click on edit

Copy the URL

Step 6:

Configuring a web server as Reverse Proxy

On your EC2 instance, install Nginx web server

sudo apt update -y && sudo apt install nginx -y

Configure the Web Server to Serve your S3 app directly and forward request to your S3 bucket

sudo vim /etc/nginx/sites-available/mybucket

Paste the configuration code snippet below and replace the highlighted part with your S3 link

 server {
    listen 80;
    server_name 100.26.55.173;  # Replace with your domain name or server IP address

    location / {
        proxy_pass https://your-bucket-name.s3.amazonaws.com; # Replace with the link you generated after you enabled  static web hosting for your bucket
        proxy_set_header Host your-bucket-name.s3.amazonaws.com;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Note Make sure to replace the link above with the link you generated after you enabled static web hosting for your bucket

Step 7:

Make your index.html public

Navigate to the index.html file, click on Action and then click on Make Public

Step 8:

Launch

insert this code to link the files
sudo ln -s /etc/nginx/sites-available/mybucket /etc/nginx/sites-enabled
Then Restart the nginx
sudo systemctl restart nginx

Copy your Public URL and paste into your browser

Contributing to Open-Source Projects on GitHub: A Step-by-Step Guide to Successfully Adding to Existing Code

Oluwatobi — Fri, 26 Jul 2024 15:14:33 +0000

Are you interested in contributing to open-source projects on GitHub but unsure where to start? This guide will walk you through successfully adding to existing code on GitHub using Git. Learn how to navigate the GitHub interface, fork and clone repositories, change existing code, and submit pull requests. Whether you're a seasoned developer or a beginner, this guide will give you the skills and confidence to contribute to open-source projects and collaborate with other developers on GitHub.

Tips:

Fork the repository to create a personal copy
Clone the forked repository using SSH (or HTTPS/GITCLI)
Ensure to configure SSH on your GitHub

Step 1:
Copy ssh URL

Step 2:
Clone (download) on your local repository (gitbash)
using
git clone "paste the ssh URL copied from github"

Step 3:
Ensure it's downloaded by running a command

ls

Step 4:
The cd into the directory

Step 5: Create a branch
git checkout -b feature/update-events

Step 6:
ls to see the list of files and what you're editing

Step 7:
Edit the file using Vim

Step 8:
Insert your edit by pressing I, after save and exit using escape, then :wq! and enter

Step 9:
Check the status of your edit by using
git status

Step 10:
Add the file by using
git add "name of the file"

Then, confirm it added but using git status again

Step 11: Commit changes and also add a message
git commit -m "whatever changes you made"

Step 12: Push your update
git push

you might have an error, but don't panic just copy the name suggested and run the command again.

You've successfully made a pull request

Step 13:
Go back to your GitHub to compare & pull request

Remember, contributing to open-source projects is a great way to collaborate with other developers, learn new skills, and build your portfolio. Don't be afraid to explore and contribute to different projects on GitHub.

How to install AWS CLI on Windows

Oluwatobi — Fri, 23 Feb 2024 16:52:58 +0000

The AWS CLI, or Command Line Interface, is a powerful tool for interacting with AWS services directly from your Windows machine. This guide will walk you through two primary methods for installing the latest AWS CLI version 2 on your Windows system.

Method 1: Using the Installer

1. Download the Installer:

Head to the official AWS CLI website: https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html

Click on Windows Option
Click the Download link and save the installer file.

2. Run the Installer:

Locate the downloaded installer file.

Double-click the file to launch the installation process.
Follow the on-screen instructions, accepting the terms and conditions.
Choose the installation location (default is recommended).
Select the components you want to install (default is recommended).
Complete the installation.

3. Verify Installation:

Open a Command Prompt window.

Type aws --versionand press Enter.
If the installation was successful, you should see the installed AWS CLI version and other details.

Method 2: Using Pip (Python Package Manager)

1. Install Python (if not already installed):

Download and install Python from https://www.python.org/.
Ensure you add Python to your PATH environment variable during installation.

2. Install the AWS CLI with Pip:

Open a Command Prompt window.
Type pip install awscli --upgrade --user and press Enter.
This will download and install the latest AWS CLI version using Pip.

3. Verify Installation:

Open a Command Prompt window.
Type aws --version and press Enter.
If the installation was successful, you should see the installed AWS CLI version and other details.

Conclusion

Whether you're a seasoned developer or just starting with AWS, the AWS CLI offers a powerful and efficient way to manage your resources. By following these steps and exploring the official documentation, you can unlock the full potential of this versatile tool and streamline your interactions with the AWS cloud platform.

Understanding Network services: FTP, SFTP, TFTP, NTP, DNS DHCP

Oluwatobi — Mon, 06 Nov 2023 18:11:48 +0000

As a Cloud, DevOps Engineer, it is necessary to have a deep understanding of various network services that play a vital role in the infrastructure of cloud-based applications. This write-up will delve into some key network services: FTP, SFTP, TFTP, NTP, DNS, and DHCP. We will explore their functions and their significance in cloud environments.

FTP (File Transfer Protocol)

Is a standard network protocol used to transfer files between a client and a server.
Users can upload or access files, organize their directories, and carry out basic file functions.

Significance in Cloud DevOps:
It is essential for migrating data to and from cloud storage

SFTP (Secure File Transfer Protocol)

Is a secure extension of FTP that uses an encrypted SSH connection for data transfer. It provides a more secure and reliable way to transfer files over a network

Significance in Cloud DevOps:
It is used for secure access to cloud-based storage and servers.

TFTP (Trivial File Transfer Protocol)

TFTP is a simplified version of FTP, primarily used for quickly transferring small files without the authentication and security features found in FTP or SFTP.

Significance in Cloud DevOps:
It supports the automation of cloud infrastructure deployment and configuration.

NTP (Network Time Protocol)

NTP is a protocol used to synchronize the time of networked devices in a distributed and accurate manner.

Significance in Cloud DevOps:
NTP ensures that logs, metrics, and events generated by cloud resources are accurately timestamped, facilitating troubleshooting and incident response.

DNS (Domain Name System)

DNS is used to translate human-readable domain names into IP addresses, making it possible for users to access websites and services by name.

DNS enables users to access websites and services using domain names like "www.google.com" instead of IP addresses “192.22.3…”

Significance in Cloud DevOps:
It is used for configuring custom domains for cloud services and applications.

DHCP (Dynamic Host Configuration Protocol)

DHCP is a network protocol that automates the assignment of IP addresses and other network configuration settings to devices on a network.

Significance in Cloud DevOps:
It supports the rapid scaling and deployment of cloud resources by automating IP address allocation.

Conclusion

Therefore, as a Cloud DevOps Engineer, one should have in-depth knowledge of such network services as FTP, SFTP, TFTP, NTP, DNS, and DHCP so as to guarantee the dependability, safety, and efficiency of cloud-based applications. Cloud service involves transfers, time synchronization, name resolution, and net configurations; all integral aspects of any modern cloud architecture. You should include those services in your DevOps practices to make your deployment process easier and operate your cloud resources smoothly.

Logging into Your AWS Console as an IAM User: Importance and Best Practices

Oluwatobi — Sat, 04 Nov 2023 15:55:55 +0000

Introduction

Amazon Web Services (AWS) provides a range of cloud services that enable organizations to create deploy and oversee applications and infrastructure, with flexibility and scalability. To ensure security and ease of management AWS utilizes Identity and Access Management (IAM) to regulate user access to AWS resources. IAM allows organizations to assign permissions to users, groups, and roles guaranteeing that individuals and systems have the level of access they require while upholding security.

Logging into your AWS Console as an IAM user is an aspect of overseeing your AWS environment. There are thousands of Videos and write-ups on how to create an IAM user on AWS, This informative article delves into the process of logging in as an IAM user elaborates on its significance, and presents practices, for user management.

The Importance of Logging in, as an IAM User

1. Security
Logging in, as an IAM user is highly important to uphold the security of your AWS environment. By granting users the permissions you minimize the potential harm that could occur if an account is compromised. IAM ensures that the principle of privilege is followed, guaranteeing that users can only access what they truly need for their designated tasks.

2. Dividing Responsibilities
IAM users enable you to distribute responsibilities within your organization. Various users can be given permissions to oversee groups of AWS resources thereby minimizing the possibility of purposeful misuse.

3. Handling Growth
As your organization expands it becomes crucial to have the capability of setting up and overseeing IAM users. This allows you to easily accommodate staff members, third-party contractors, and automated systems while maintaining a grip, on resource access.

4. Accountability
IAM user logins contribute to accountability and auditing. Each login event is recorded, including the user's actions within the AWS environment. This audit trail is invaluable for compliance, troubleshooting, and security investigations.

Best Practices for Secure IAM User Management

Use Strong Passwords: Make use of strong and unique passwords.

Implement MFA: Authorise the use of Multi-Factor Authentication for all IAM users. This provides an additional layer of security against unauthorized access.

Permission-based Principle: Assign IAM permissions based on the principle of least privilege. Only grant users the permissions they need to perform their tasks.

Use Groups: Organize IAM users into groups with similar responsibilities and permissions. This simplifies user management and ensures consistency.

Regularly Monitor: Continuously monitor user activity and regularly review access logs to detect and respond to suspicious or unauthorized behavior.

Implement IAM Policies and Roles: Create IAM policies and roles to define fine-grained permissions for users. Roles are especially useful for granting temporary permissions to resources.

Stay Informed: Keep abreast of AWS best practices, security updates, and new IAM features to continually improve security.

Conclusion

Logging into the AWS Console as an IAM user is not just a matter of convenience; it's a critical aspect of managing your AWS environment securely. By following best practices for IAM user management and consistently adhering to security guidelines, organizations can harness AWS's powerful cloud resources while minimizing risks and ensuring a robust security posture.

Why Is Bash scripting an important tool to learn as a Cloud DevOps engineer?

Oluwatobi — Mon, 02 Oct 2023 00:46:05 +0000

Bash is widely regarded as a universal scripting language
In the world of cloud computing. All cloud platforms support using Bash commands to pass data and information. Bash scripting is mainly used for Automating tasks in DevOps workflow.

Let’s establish what Shell scripting and Bash scripting are:
Shell scripting is the practice of writing scripts or programs using a shell's scripting language.

Bash scripting, short for “Bourne Again SHell” is a subset of shell scripting language.

Importance of Bash scripting

Automation: It allows you to create scripts that can execute a series of commands automatically. This is indispensable for tasks that need to be repeated regularly, such as backups, log file parsing, and system maintenance.
Efficiency: They can perform complex tasks quickly and consistently, reducing the potential for human error.
Remote Administration: Bash scripts can be used for remote administration of systems. With tools like SSH, you can run Bash scripts on remote servers, making it easier to manage and maintain multiple systems.
Logging and Reporting: Bash scripts can generate logs and reports, which are essential for monitoring system health, tracking changes, and troubleshooting issues.

Having established some relevant importance of bash scripting,

How do we identify a Bash script?

Every bash script starts with a shebang/hashbang #! at the very beginning of a script file to indicate the path to the interpreter that should be used to execute the script.
#! /bin/bash/

#! tells the system to use the Bash shell interpreter to run the script. The shebang line is crucial because it ensures that the script is executed with the correct interpreter, regardless of where the script is located.

Note: Different interpreters, such as Python, Perl, or Ruby, may have their own shebang lines.

Conclusion

By understanding the importance of Bash scripting and recognizing its distinctive shebang notation, you can harness this tool effectively to manage and maintain cloud-based systems with precision and reliability.

Next write-up, I’ll be discussing the Bash scripting Fundamental concepts and skills to focus on.

How can I learn Linux without using any Cloud platforms?

Oluwatobi — Tue, 12 Sep 2023 17:09:12 +0000

Having established that learning Linux is an important prerequisite for working on cloud platforms, it's worth noting that Linux cloud-based environments offer services involving a subscription fee. However, using Linux on a Windows machine is an alternative way of effectively learning Linux at no cost.

What are Windows machines?

Window machines are desktops and laptop that run the Windows Operating system (OS).

How can Linux OS work on windows machines?

This is possible through a concept/technology called Virtualization. Virtualization is like running multiple separate computers (virtual machines) on a single physical computer. Each virtual machine behaves like an independent computer with its own operating system and applications, even though they all share the underlying hardware resources of the physical computer. The virtualization process is made possible by a hypervisor.

Hypervisors are divided into two types, namely;

Type 1 hypervisor (bare metal)
Type 2 hypervisor (hosted)

With Type 2 hypervisors being our main focus, let’s briefly discuss the two types of hypervisors.

A Type 1 hypervisor runs directly on the physical computer, It's like having a boss who manages employees {virtual machines} without any middle managers {OS} in between.

On the other hand, a Type 2 hypervisor, Is a software you install into your usual Windows OS, and it helps you create and run virtual machines.

Examples of Type 2 hypervisors include;

Oracle Virtual box: It is the most used and popular open-source Type 2 Hypervisor that works on various operating systems, including Mac.
VMware Workstation: VMware is known for its performance and feature set.
Parallel Desktops: It is specifically designed for Mac computers and allows you to run Windows and other operating systems alongside macOS.
Microsoft Virtual PC: This is a Type 2 hypervisor provided by Microsoft, primarily for Windows-based systems.

I strongly recommend using Oracle Virtual Box as your hypervisor.

Conclusion

In conclusion, learning Linux without relying on cloud platforms is entirely possible, and using Linux on a Windows machine is an efficient way to learn Linux.