<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Alhaji Bah on Medium]]></title>
        <description><![CDATA[Stories by Alhaji Bah on Medium]]></description>
        <link>https://medium.com/@alhaji_8801?source=rss-51c5cf2a7669------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ykdE5a0Jex7n3e--tfX1pA.png</url>
            <title>Stories by Alhaji Bah on Medium</title>
            <link>https://medium.com/@alhaji_8801?source=rss-51c5cf2a7669------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:01:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alhaji_8801/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Deploy a Jenkins Server w/ Terraform.]]></title>
            <link>https://blog.devops.dev/deploy-a-jenkins-server-w-terraform-2350e04576cb?source=rss-51c5cf2a7669------2</link>
            <guid isPermaLink="false">https://medium.com/p/2350e04576cb</guid>
            <category><![CDATA[ec2]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Alhaji Bah]]></dc:creator>
            <pubDate>Mon, 11 Nov 2024 22:20:38 GMT</pubDate>
            <atom:updated>2024-11-15T18:15:49.830Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*jJCkos_lHG8LrEUNb-EiSA.png" /></figure><p><strong>Scenario:</strong></p><p>You and your team have agreed to utilize Jenkins as the CI/CD tool to streamline DevOps projects. The goal is to create the Jenkins server for other environments using Terraform. We will need to deploy an EC2 instance within a default VPC while bootstrapping the EC2 instance with a script that will install and start Jenkins. We will be using a single <em>main.tf</em> file (monolith) for the hardcoded data.</p><p>For security, we will create and assign a Security Group to the Jenkins Security Group, which will allow traffic on port 22 from an IP address and allow traffic from port 8080. We will create a private S3 bucket to store the Jenkins Artifacts and will verify that we can reach the Jenkins server installed on port 8080.</p><p><strong>Defining some KEY terms:</strong></p><p><em>Infrastructure-as-Code (IaC):</em> The practice of provisioning and managing infrastructure defined through code instead of a manual process. This process provides software development benefits such as code reusability, version control, infrastructure management, automation, etc.</p><p><em>Terraform: </em>A powerful and popular IaC tool by Hashicorp. This tool is cloud-agnostic (Used in AWS, GCP, Azure, Oracle, Alibaba, etc.) and manages the lifecycle of your infrastructure by updating, deleting, and provisioning resources based on the definitions in the code. Terraform decided what order to process objects mentioned in the configuration files based on a combination of analyzing dependencies.</p><p><strong>Prerequisite:</strong></p><ul><li>IDE (We will be using VS Code for this project)</li><li>Terraform is installed on a local machine.</li><li>An EC2 instance.</li><li>A bootstrap with a script to install Jenkins.</li><li>Created a Security Group for Jenkins.</li><li>S3 bucket with Jenkins Artifacts stored.</li><li>main.tf file with the required configuration block</li><li>GitHub account to push the Jenkins code into a new repository.</li></ul><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>To begin, access the IDE of your choosing and install Terraform. (This will be specifically for Ubuntu/Debian)</p><p>First, add the HashiCorp GPG key.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/659/1*d30_xFtvhL1Tlbg5pUrw6Q.png" /></figure><pre>curl -fsSL https://apt.releases.hashicorp.com/gpg | sudo apt-key add -</pre><p>Then, add the HashiCorp Linux repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*AEr0MVKAQwozGo0az3DYTw.png" /></figure><pre>sudo apt-add-repository &quot;deb [arch=amd64] https://apt.releases.hashicorp.com $(lsb_release -cs) main</pre><p>Update and Install Terraform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/532/1*j6MkyA1giopO-eZLZb4E1A.png" /><figcaption>Update and Install the current version of Terraform.</figcaption></figure><p>Next, verify the version of Terraform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*NeMFxLQkv6gshDN8nkBr5g.png" /><figcaption>View the current version of Terraform.</figcaption></figure><p>We will create a directory for our Jenkins project. Once created, we will change into the newly created directory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/357/1*vnoJ42o03dl5zqrL5XHu5w.png" /><figcaption>Make the directory</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/357/1*rKUt7hXg9SeCJ7Z8RJwJBg.png" /><figcaption>Change into the directory.</figcaption></figure><pre>mkdir Jenkins-Project<br>cd Jenkins-Project</pre><p>Let’s create the main.tf file in the Jenkins-Project folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/372/1*hSFjzlsQR5STqTvINQGuFg.png" /><figcaption>Create the main.tf file</figcaption></figure><pre>touch main.tf</pre><p>Let’s create a Variable file for configuration, an Outpost configuration file, and a bootstrap script file for the Jenkins installation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/472/1*PJiMQDvUqN_OPCFAL66XCA.png" /><figcaption>Create the three files for configuration.</figcaption></figure><pre>touch variables.tf<br>touch outpost.tf<br>touch jenkins_bootstrap.sh</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/209/1*TjW-YiF6ydxom6umPD3-VA.png" /><figcaption>View all the created files.</figcaption></figure><p>Let’s open the Bootstrap Jenkins file configuration to add the Jenkins script to start the Jenkins server. You can find the script on the Jenkins home page <a href="https://www.jenkins.io/doc/tutorials/tutorial-for-installing-jenkins-on-AWS/">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*oCTtLky5nUJw1h75ma3dWQ.png" /><figcaption>Add the Jenkins Bootstrap script with the comments provided.</figcaption></figure><pre>sudo yum update –y<br>sudo wget -O /etc/yum.repos.d/jenkins.repo \<br>    https://pkg.jenkins.io/redhat-stable/jenkins.repo<br>sudo rpm --import https://pkg.jenkins.io/redhat-stable/jenkins.io-2023.key<br>sudo yum upgrade<br>sudo dnf install java-17-amazon-corretto -y<br>sudo yum install jenkins -y<br>sudo systemctl enable jenkins<br>sudo systemctl start jenkins<br>sudo systemctl status jenkins</pre><p>Next, define the variables that will customize aspects of the infrastructure. Terraform variables are essentially placeholders for values that make the configurations dynamic and reusable. You can use variables to achieve different use cases, and they are extremely viable for building scalable, maintainable, and adaptable infrastructure configurations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*blwP54CPU14l6XuaUpZ-Kg.png" /><figcaption>You can see where the AWS region, Instance Type, AMI ID, SSH Key pair, and access to the allowed IP address are formed.</figcaption></figure><pre><br>variable &quot;region&quot; {<br>  description = &quot;The AWS region to deploy resources in&quot;<br>  default     = &quot;us-east-1&quot;<br>}<br><br>variable &quot;instance_type&quot; {<br>  description = &quot;EC2 instance type&quot;<br>  default     = &quot;t2.micro&quot;<br>}<br><br>variable &quot;ami&quot; {<br>  description = &quot;AMI ID for the Amazon Linux 2 server&quot;<br>  default     = &quot;ami-063d43db0594b521b&quot;<br>}<br><br>variable &quot;key_name&quot; {<br>  description = &quot;Name of the SSH key pair&quot;<br>}<br><br>variable &quot;allowed_ip&quot; {<br>  description = &quot;Your IP address to allow SSH and Jenkins access&quot;<br>}</pre><p>Add data for the Output file containing the public IP address of the EC2 instance and S3 bucket name for easy reference for the Terraform deployment. Terraform Output contains the output values that are information to expose within a Terraform configuration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*10vYtV2PomHAeU_uneCb8A.png" /></figure><pre><br>output &quot;jenkins_instance_public_ip&quot; {<br>  description = &quot;Public IP of the Jenkins EC2 instance&quot;<br>  value       = aws_instance.jenkins.public_ip<br>}<br><br>output &quot;jenkins_url&quot; {<br>  description = &quot;URL to access Jenkins&quot;<br>  value       = &quot;http://${aws_instance.jenkins.public_ip}:8080&quot;<br>}<br><br>output &quot;s3_bucket_name&quot; {<br>  description = &quot;Name of the S3 bucket for Jenkins artifacts&quot;<br>  value       = aws_s3_bucket.jenkins_artifacts.bucket<br>}</pre><p>Lastly, we can start creating our resources in the main.tf file.</p><p>The main.tf is the prime configuration where you completely detailed the infrastruture resources.</p><p>In the provider block, we have AWS configured as the provider and specified the region. The security group “aws_security_group” and “jenkins_sg” will allow SSH access (port 22) and Jenkins access (port 8080) only from the designated IP address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/973/1*Es-PmuCIKYdkZLv3bOBNtA.png" /><figcaption>The provider block and security group for the EC2 instance.</figcaption></figure><pre>provider &quot;aws&quot; {<br>  region = &quot;us-east-1&quot;<br>}<br><br>resource &quot;random_id&quot; &quot;bucket_id&quot; {<br>  byte_length = 8<br>}<br><br>resource &quot;tls_private_key&quot; &quot;jenkins_key&quot; {<br>  algorithm = &quot;RSA&quot;<br>  rsa_bits  = 2048<br>}<br><br>resource &quot;local_file&quot; &quot;jenkins_private_key&quot; {<br>  content  = tls_private_key.jenkins_key.private_key_pem<br>  filename = &quot;/Users/alhajib/Jenkins-project/JenkinsKey.pem&quot;<br>}<br><br>resource &quot;aws_key_pair&quot; &quot;jenkins_key&quot; {<br>  key_name   = &quot;JenkinsKey&quot;<br>  public_key = tls_private_key.jenkins_key.public_key_openssh<br>}<br><br>resource &quot;aws_security_group&quot; &quot;jenkins_sg&quot; {<br>  name_prefix = &quot;jenkins-sg&quot;<br>  description = &quot;Security group for Jenkins&quot;<br>  vpc_id      = &quot;vpc-0601b102bb3b5b175&quot; <br><br>  ingress {<br>    from_port   = 22<br>    to_port     = 22<br>    protocol    = &quot;tcp&quot;<br>    cidr_blocks = [&quot;96.231.150.247/32&quot;] <br>  }<br><br>  ingress {<br>    from_port   = 8080<br>    to_port     = 8080<br>    protocol    = &quot;tcp&quot;<br>    cidr_blocks = [&quot;0.0.0.0/0&quot;] <br>  }<br><br>  egress {<br>    from_port   = 0<br>    to_port     = 0<br>    protocol    = &quot;-1&quot;<br>    cidr_blocks = [&quot;0.0.0.0/0&quot;]<br>  }<br>}</pre><p>The EC2 instance “aws_instance” and “jenkins” (the name of the EC2 instance) will be using the Amazon Linux 2 AMI ID to install and start Jenkins. We have an S3 bucket “aws_s3_bucket” and “jenkins_artifacts” created where we will store all the artifacts related to Jenkins, it will be configured as a private bucket and will allow versioning in case of accidental deletion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*Aw9z0sptJH37s6tXe_5T1w.png" /><figcaption>The creation of the EC2 instance and S3 bucket.</figcaption></figure><pre><br>resource &quot;aws_instance&quot; &quot;jenkins&quot; {<br>  ami             = (AMI ID HERE)<br>  instance_type   = var.instance_type<br>  key_name        = var.key_name<br>  security_groups = [aws_security_group.jenkins_sg.name]<br><br>  user_data = file(&quot;jenkins_bootstrap.sh&quot;)<br><br>  tags = {<br>    Name = &quot;JenkinsServer&quot;<br>  }<br>}<br><br>resource &quot;aws_s3_bucket&quot; &quot;jenkins_artifacts&quot; {<br>  bucket = &quot;jenkins-artifacts-${random_id.bucket_id.hex}&quot;<br>}<br><br>resource &quot;aws_s3_bucket_acl&quot; &quot;jenkins_acl&quot; {<br>  bucket = aws_s3_bucket.jenkins_artifacts.id<br>  acl    = &quot;private&quot;<br>}</pre><p>Once the codes have been placed, let’s first format it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/534/1*k68ylAO76oZUHpvj5HziLw.png" /><figcaption>Format the code so it’s terraform formatted.</figcaption></figure><pre>terraform fmt</pre><p>Now, we can initialize the files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/534/1*k68ylAO76oZUHpvj5HziLw.png" /></figure><pre>terraform init</pre><p>We can validate that everything is ready for creation for the Jenkins server.</p><pre>terraform validate</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/411/1*WxWODxPaj4yr9WQpM9xnoQ.png" /></figure><p>Now, let’s plan out what resources will be created.</p><pre>terraform plan</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vg7fY-kNxQFc8b3Cr8WjqQ.png" /><figcaption>You can see all the resources Terraform identifies for creation.</figcaption></figure><p>FINALLY, let’s create all the resources at once.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/491/1*r_H6YKFq_hiESGm1I-lIXg.png" /><figcaption>We are adding Auto Approve to allow the services to be created without manual approval.</figcaption></figure><p>Once the infrastructure has been created, let’s verify that the Jenkins service is up and running.</p><pre>sudo systemctl status jenkins</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*0rS9ahObZQW9IkLHlrnQJg.png" /></figure><p>Go to your browser and paste this address http<a href="http://http//your">://(your</a> public IP address):8080 to access the Jenkins server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UvdEx6yJqFG-DwTwGPOLMA.png" /></figure><p>Congratulations! You were able to successfully deploy a Jenkins Server using Terraform! You and your team of bright engineers were able to brilliantly configure a Terraform template to create an EC2 server, an S3 bucket, security groups to allow traffic into the server, and fully deploy a Jenkins server in the Ec2 instance.</p><p>Thank you for taking the time to navigate Terraform with me, I hope you find this help in your DevOps Cloud journey. If you did find this article helpful in any way, please send a clap to this article or follow me for more tips and tricks inside the cloud industry at <a href="https://www.linkedin.com/in/alhaji-bah/">Alhaji Bah | LinkedIn</a>. You can also take a look at my repo on GitHub <a href="https://github.com/AlhajiB3/Jenkins_Terraform.git">here</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2350e04576cb" width="1" height="1" alt=""><hr><p><a href="https://blog.devops.dev/deploy-a-jenkins-server-w-terraform-2350e04576cb">Deploy a Jenkins Server w/ Terraform.</a> was originally published in <a href="https://blog.devops.dev/">DevOps.dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Docker to Jenkins: Installing Docker inside a Jenkins container]]></title>
            <link>https://blog.devops.dev/from-docker-to-jenkins-installing-docker-inside-a-jenkins-container-eb5b8fa57e77?source=rss-51c5cf2a7669------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb5b8fa57e77</guid>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Alhaji Bah]]></dc:creator>
            <pubDate>Mon, 21 Oct 2024 12:57:25 GMT</pubDate>
            <atom:updated>2024-10-22T16:16:02.301Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7ZSIFLXHn-HQmePS.png" /><figcaption>Photo cred <a href="https://www.tothenew.com/blog/automated-docker-deployment-using-jenkins/">here</a>.</figcaption></figure><p><strong>SCENARIO:</strong></p><p>Imagine you’re running a Jenkins CI/CD pipeline, and you realize you need <a href="https://aws.amazon.com/docker/#:~:text=Docker%20lets%20you%20build,%20test,%20and%20deploy%20applications%20quickly&amp;text=Using%20Docker,%20you%20can%20quickly,distributed%20applications%20at%20any%20scale.">Docker</a> installed on the Jenkins container to manage your build and deployment processes. By default, Docker isn’t installed. How do you overcome this challenge? If you’ve read this far, you are in the right article.</p><p>The plan is to build a robust, scalable, Continuous Integration and Continuous Deployment (CI/CD) pipeline, initiating frequent and reliable software update deployments. This strategy will provide significant advantages in terms of cost savings, consistency, and reliability.</p><p>Jenkins is an open-sourced automation tool used to orchestrate build process steps. When you want to build and deploy your application, you will need to run a series of commands to perform various tasks: building your Docker image, starting your container, deploying your application, etc. Just like in CI/CD, you can merge and push changes, and Jenkins will help you automate all of it.</p><p><strong>OBJECTIVES:</strong></p><ol><li>Pull the Jenkins LTS image from the Docker Hub.</li><li>Create a Docker volume for Jenkins to persist its data.</li><li>Run the container with the volume and correct port mapped to the container.</li><li>Retrieve the Admin password.</li><li>Login and create a new user.</li><li>Launch a new Jenkins container using the same volume and verify that the data has persisted by logging in as a newly created user.</li></ol><p><strong>STEP 1: Pull the Jenkins LTS Image from the Docker Hub.</strong></p><p>Find the<a href="https://hub.docker.com/"> Docker Hub website </a>and search for the Jenkins image to pull to create our base image for the Docker container.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/776/1*yLBSZ5GH6pRmoVdMNfPWdg.png" /><figcaption>In the Docker Hub, search for the latest Jenkins image.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/1*iFal6yJBZt41kZV9GwiinA.png" /><figcaption>Copy the command and run. You should see the newest image downloaded.</figcaption></figure><pre>docker pull jenkins/jenkins:lts-jdk17</pre><p><strong>STEP 2: Create a Docker volume for Jenkins to persist its data.</strong></p><p>You will create an explicit docker volume to prevent all of your data from being deleted when you restart the container.</p><pre>docker volume create --name</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/519/1*dexSAKozHV8IDKW47h8JFQ.png" /><figcaption>Create the volume attached to the Jenkins container</figcaption></figure><p><strong>STEP 3: Run the container with the volume and correct port mapped to the container.</strong></p><p><em>(Note: parenthesis were placed on the names of the Jenkins container and the volume name).</em></p><pre>docker run --name (jenkins_LUIT) -d -p 8080:8080 -v (dockerjenkinsvolume):/var/jenkins_home jenkins/jenkins:lts-jdk17</pre><p>Here is a full breakdown of each command:</p><p><strong>(docker run)</strong>— we are starting the process of running the Jenkins container.</p><p>( <strong>— name</strong>) — we have a naming convention for our Jenkins container (jenkins_LUIT).</p><p>(<strong>-d</strong>) — the container should be in detached mode, meaning it will continue to run in the background of the terminal, and no input or output will be displayed.</p><p>(<strong>-p 8080:8080</strong>) — maps the port 8080 onto the host port 8080 on the container.</p><p>(-<strong>v dockerjenkinsvolume:/var/jenkins_home</strong>) — this adds to the created volume (dockerjenkinsvolume) from the host ‘/var/jenkins_home’ in the container.</p><p>(<strong>jenkins/jenkins:lts-jdk17) </strong>— this is our created image for our Jenkins container.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1005/1*XqidVO4xjSTDcBbsdoojVg.png" /><figcaption>To start the Jenkins container, you must run and understand why we are using these commands to start the container.</figcaption></figure><p>To confirm that the Jenkins container is running:</p><pre>docker ps -a</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1005/1*kUDkY84aq9yvxkmerbH7WQ.png" /></figure><p>Let’s connect to our Jenkins container! Copy the EC2 instance IP address and paste it on a URL (http://ec2 instance:8080)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jn87bua48Cb8fgef_lET8g.png" /><figcaption>Once connected, you will be prompted to the Jenkins login page</figcaption></figure><p><strong>STEP 4: Retrieve the Admin password.</strong></p><p>You will need to retrieve the admin password to access Jenkins.</p><p>You can find the admin password by using the docker logs command. To view the log information regarding the Jenkins container:</p><pre>docker logs (name of the container)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*KPfMogD1rcgEnCpt21lm3w.png" /><figcaption>You will find the log information and the admin password with the docker logs.</figcaption></figure><p>Another example of finding the admin password is by navigating to the Jenkins Home Directory and retrieving it that way.</p><p>We need to start by running a command to access the container’s shell.</p><pre>docker exec -it jenkins_LUIT /bin/bash</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/476/1*r8aIw-6yAUdHWtUKxhQLnA.png" /><figcaption>This command will give you access to the interactive shell of the container.</figcaption></figure><p>Now, we can move into the Jenkins Home Directory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/385/1*0jCpoI9o_jf-lfNeg8_SVA.png" /></figure><pre>cd /var/jenkins_home/secrets/</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/484/1*lKkGRX0AQhx10VM2vyUHXg.png" /><figcaption>After changing the directory in the Jenkins Home Directory, list the files in the directory.</figcaption></figure><p>Now, let’s view the contents of the file to view the admin password.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/471/1*pdwosOgBrInezFrc79zo4Q.png" /></figure><p>Copy the admin password and paste it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i9bbEv8wyAVlNuObsuHUwg.png" /><figcaption>Paste the password here to move to the next stages.</figcaption></figure><p><strong>STEP 5: Login and create a new user.</strong></p><p>Simply choose “Install suggested plugins”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ie1mHxXjtgmERM6y6colHg.png" /><figcaption>Click Install suggested plugins.</figcaption></figure><p>Follow the instructions to create the First Admin User.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I7LeSy6B85FrzNwQLqbJyA.png" /><figcaption>Enter information to create a new user.</figcaption></figure><p>We are getting closer! Once that information has been entered, you will receive this prompt to start using Jenkins.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k3iG-Gp3lgGf2Wjd0AAavQ.png" /><figcaption>You are ready to enter the Jenkins container and view the interface.</figcaption></figure><p><strong>STEP 6: Launch a new Jenkins container using the same volume and verify that the data has persisted by logging in as a newly created user.</strong></p><p>To complete this, let’s completely stop the first Jenkins container.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/431/1*7R5jMWFfP0UMAJM4hHgkmA.png" /></figure><pre>docker container stop (name of the container)</pre><p>Next, let’s create a brand new Jenkins container using the same created volume.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/977/1*030Q-0zPiIIYfHX7AxF6Ww.png" /></figure><pre> docker run --name (jenkins2_LUIT) -d -p 8080:8080 -v (dockerjenkinsvolume):/var/jenkins_home jenkins/jenkins:lts-jdk17</pre><p><em>(Note: parenthesis were placed on the names of the second Jenkins container and created volume name).</em></p><p>Arrive back to the URL where the Jenkins container is being held. Enter the credentials you created from the first Jenkins container.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bl9JX43mZn-mr8C678nXlg.png" /><figcaption>You will be prompted to enter the same credentials you used when creating the first admin.</figcaption></figure><p>After entering the credentials, wait to see the output…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2QVbvDQ6OkNaDrQGumHF6g.png" /></figure><p>Congratulations!! You have successfully run a docker container using the same volume and verified that the data has persisted !!</p><p>Remember, when finished, stop and remove the container.</p><pre>docker container stop (name of the second container)<br><br>docker container rm (name of containers)</pre><p>We can stop both containers and remove both containers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/1*HLAV8-J6BSJ1UHwtYU0zOg.png" /></figure><p>Once you remove the container, remove the Jenkins image.</p><pre>docker image rm </pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/1*49IHieMCwswjHV43mHAChw.png" /></figure><p>You have safely removed the Jenkins image.</p><h3>-BONUS- Using DOCKER COMPOSE</h3><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Docker Compose is a tool that allows you to define and run multi-container Docker applications. You can configure services within a single YAML file (<em>docker-compose.yml</em>). The file describes the services, volumes, and networking components necessary when organizing and managing multiple containers.</p><p>To start, let’s go ahead and create a directory for our docker-compose file.</p><pre>mkdir (name of the directory)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/353/1*NW5OHQFgG3UwX2iIEceYWQ.png" /><figcaption>Make the directory, then change it into that directory.</figcaption></figure><p>Next, we can create the docker-compose file.</p><pre>touch docker-compose.yml</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/451/1*YRH7VirAbEisvHYSwEz8Yw.png" /><figcaption>Create the docker-compose file.</figcaption></figure><p>Edit the docker compose file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/451/1*1DX2bycZcT8lnyEdHvzj3A.png" /><figcaption>Edit the docker-compose file.</figcaption></figure><p>Let’s add information for our YAML file with the Jenkins image, container name, ports, volumes, and network.</p><pre>version: &#39;3&#39;<br>services:<br>  jenkins:<br>    image: jenkins/jenkins:lts<br>    container_name: jenkins-compose<br>    ports:<br>      - &quot;8080:8080&quot;<br>    volumes:<br>      - jenkins_data:/var/jenkins_home<br>      - /var/run/docker.sock:/var/run/docker.sock<br>    networks:<br>      - jenkins_network<br><br>volumes:<br>  jenkins_data:<br><br>networks:<br>  jenkins_network:</pre><p>Now run the docker-compose command.</p><pre>docker compose up</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1005/1*0c0Nvv4wrq_RdOpDypdc6Q.png" /><figcaption>Run the command to create all the resources in the YAML file.</figcaption></figure><p>You will go through the entire process once you are prompted to enter the admin password.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RXVeR1r_Ud0EiQng9NDzLg.png" /></figure><p>Lastly, let’s clean up everything and shut everything off.</p><pre>docker compose down</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/486/1*OhsAodBu9iv-ZdUeCqc1-w.png" /><figcaption>Run the docker-compose down command to stop the running of that Jenkins container.</figcaption></figure><p>Thank you for taking the time to view these Docker and Jenkins builds with me. If you found this article helpful, please provide a follow to this medium page or send a clap to increase viewership. If you would like to get more tips and tricks on the cloud industry, please send an invite to my LinkedIn at <a href="https://www.linkedin.com/in/alhaji-bah/">Alhaji Bah | LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb5b8fa57e77" width="1" height="1" alt=""><hr><p><a href="https://blog.devops.dev/from-docker-to-jenkins-installing-docker-inside-a-jenkins-container-eb5b8fa57e77">From Docker to Jenkins: Installing Docker inside a Jenkins container</a> was originally published in <a href="https://blog.devops.dev/">DevOps.dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s create an Apache Web Server in a Docker Container]]></title>
            <link>https://blog.devops.dev/lets-create-an-apache-web-server-in-a-docker-container-9eea68af26d0?source=rss-51c5cf2a7669------2</link>
            <guid isPermaLink="false">https://medium.com/p/9eea68af26d0</guid>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[containerization]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Alhaji Bah]]></dc:creator>
            <pubDate>Mon, 14 Oct 2024 15:12:55 GMT</pubDate>
            <atom:updated>2024-10-14T17:40:39.723Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Qnc6Umxrlw8wUl7O.png" /><figcaption>image creds by <a href="https://medium.com/@thegregjames">https://medium.com/@thegregjames</a></figcaption></figure><p>Level Up Solutions is a dynamic technology company that offers innovative web solutions to its clients. After careful analysis of improving their software development process, the organization has decided to adopt containerization by using <strong>Docker</strong> to help streamline the web application deployment. With Docker, Level Up Solutions can take advantage of docker’s ability to containerize an application and improve its services.</p><p><strong>What is Docker? </strong>Docker is a software platform that allows developers to build, test, and deploy applications quickly. Docker provides the ability to package and run an application in an isolated environment called a Container. Containers are lightweight and use images to run in the application. Images are a read-only template with instructions for creating the containers and most times, images are based on another image. Containers are <strong>FANTASTIC</strong> for continuous integration and continuous delivery<strong> (CI/CD) </strong>workloads.</p><p>To help out Level Up Solution’s software deployment, our team of brilliant cloud engineers will create a Docker container, install an Apache webserver, create a custom webpage and push the images to a docker-hub repository.</p><p><strong>Ingredients:</strong></p><ul><li><em>An EC2 instance with Ubuntu Image (publicly access)</em></li><li><em>Linux &amp; Docker Commands (We will be using VS Code as our integrated development environment)</em></li><li><em>Docker Container</em></li><li><em>Docker Images from the Docker registry</em></li><li><em>Docker login (Logging into a docker-hub account)</em></li><li><em>Dockerfile (we will create shortly)</em></li><li><em>Index.html file for the custom webpage (we will create shortly)</em></li><li><em>A Docker-Hub repository</em></li></ul><h3>LETS GET STARTED !!!!!</h3><p>First, let’s create an EC2 instance and SSH into the instance. IF you would like a quick tutorial on completing this task, check out my medium article on <a href="https://medium.com/devops-dev/the-ssh-way-lets-create-a-secure-remote-admin-with-our-linux-ec2-instances-%EF%B8%8F-55acdf94ff6b">SSH into a EC2 instance</a>.</p><p>You will need to install the latest version of Docker first. After installing, pull the latest image ubuntu image from the docker-hub registry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/466/1*s5krYJAC1iFzfuseZfCWSw.png" /><figcaption>Connect into the EC2 instance and pull the latest ubuntu image</figcaption></figure><pre>docker pull ubuntu:latest</pre><p>You can see the latest Ubuntu image pulled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*A012KA-8OXG9XZC7hRvIWQ.png" /><figcaption>You will see the information regarding whether the image has been correctly pulled from the docker-hub repository</figcaption></figure><p>Now let’s create both Index.html and Docker files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/313/1*Z1u3HxtXOCgHMKNNd31HYw.png" /><figcaption>Create a Index.html and a dockerfile.</figcaption></figure><pre>touch index.html<br>touch dockerfile</pre><p>First, let’s edit the Index.html file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/276/1*LznfM13JoACIdXL_-4yg0w.png" /><figcaption>Use the vi text editor to edit the intended html file.</figcaption></figure><p>We have our custom html file ready to be launch (be creative when creating your custom html file.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/454/1*trPIkXvOaMPXAx9kD297-w.png" /><figcaption>After making edits, we used the cat command to view the contents of our html file.</figcaption></figure><pre>cat index.html</pre><p>In the docker file, we will need to create a set of instruction so the container can run with Apache installed and configured correctly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/467/1*BCJ35km3q3VWNFUsxwLCZA.png" /><figcaption>Let’s edit the docker file.</figcaption></figure><pre>vim dockerfile</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/1*JJcpgwj_bCHCD8Z0miu4Ww.png" /><figcaption>Each line has a comment with the instructions needed to create and run the apache server in the container.</figcaption></figure><p>For context:</p><ol><li>FROM — specifies the base image that the container will be built off of.</li><li>RUN — Executes commands in the container while building the image. The command “apt-get update” will update the package lists from Ubuntu repositories to get the latest available versions of packages. The “apt-get install -y apache 2” command installs the Apache web server. The (-y) option automatically answers &quot;yes&quot; which allows the installation to proceed without user interaction.</li><li>COPY — Copies files from your local machine to the container’s filesystem. (index.html is the source file while /var/www/html/index.html is the destination path inside the container where the Apache serves web pages for default.)</li><li>EXPOSE — Prepares the container to accept HTTP &amp; HTTPS traffic</li><li>RUN — Starts Apache in the foreground, this allows the container to be kept alive once apache starts so the container does not shut down.</li></ol><h3>We are spinning up a small Ubuntu server within seconds!</h3><p>Now we can build the custom image and run it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*h6tv6LIemJZ1i_nYL8FR_w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*T_sBzkM_FccMycCqnkvJEg.png" /><figcaption>This the created ID after detaching the apache web server</figcaption></figure><pre>docker run -d -p 8080:80 my-apache-webserver</pre><p>We will confirm that the docker container is running.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*pCBKO-oD6Baefe8vYVA-vA.png" /><figcaption>We verified that the container is running</figcaption></figure><pre>docker ps -a </pre><p>Now let’s go into our EC2 instance and see if our custom webpage is working for Level Up Solutions!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3WqvmIUNla6NjM6Z61VeEw.png" /><figcaption>Bingo ! We have successfully created an Apache Web-server with Docker.</figcaption></figure><p>Finally let’s try to push into a new repository for Docker-hub!</p><p>Since we are already logged into our Docker-hub, we will not need to login again.</p><p>First let’s tag the repo and provide a name for the repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/519/1*_iAWY7c4Uz8CZ4Q5dIc5ng.png" /><figcaption>We will need to tag this repo.</figcaption></figure><pre>docker tag my-apache-webserver abah8801/my-apache-webserver:latest</pre><p>Next let’s try pushing the image into the docker-hub.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/519/1*Dm0QigJ3KNw8Z30QSdL1tw.png" /></figure><pre>docker push abah8801/my-apache-webserver:latest</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*KG208VwbuUAqTo_3h5k9yg.png" /><figcaption>The ID at the bottom confirms the image being pushed.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lBnoRrcVMjkaHJ86Ijfcig.png" /><figcaption>View the pushed docker-hub repo</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1nlLV3uuiw7srkTW1MYncw.png" /><figcaption>View both the repo and instructions based on the container image.</figcaption></figure><p>Congratulations! You were able to help Level Up Solutions focus on utilizing docker containers and optimize their deployment processes.</p><p>Thank you for taking the time to viewing Docker and containerization as a whole. If you found this article helpful, please provide a follow to this medium page or send a clap to increase viewership. If you would like to get more tips and tricks of the cloud industry, please send an invite to my LinkedIn at <a href="https://www.linkedin.com/in/alhaji-bah/">Alhaji Bah | LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9eea68af26d0" width="1" height="1" alt=""><hr><p><a href="https://blog.devops.dev/lets-create-an-apache-web-server-in-a-docker-container-9eea68af26d0">Let’s create an Apache Web Server in a Docker Container</a> was originally published in <a href="https://blog.devops.dev/">DevOps.dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transforming Customer Feedback with AI: Leveraging Image Recognition️ and Sentiment Analysis…]]></title>
            <link>https://blog.devops.dev/transforming-customer-feedback-with-ai-leveraging-image-recognition-%EF%B8%8F-and-sentiment-analysis-759ac7d88469?source=rss-51c5cf2a7669------2</link>
            <guid isPermaLink="false">https://medium.com/p/759ac7d88469</guid>
            <category><![CDATA[azure-ai]]></category>
            <category><![CDATA[blob-storage]]></category>
            <category><![CDATA[image-recognition]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[text-analysis]]></category>
            <dc:creator><![CDATA[Alhaji Bah]]></dc:creator>
            <pubDate>Mon, 23 Sep 2024 13:21:29 GMT</pubDate>
            <atom:updated>2024-09-24T18:45:57.812Z</atom:updated>
            <content:encoded><![CDATA[<h3>Transforming Customer Feedback with AI: Leveraging Image Recognition🖼️ and Sentiment Analysis 💬for Smarter Insights</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*ABRiQzi5At0CyVWr" /></figure><p><strong>Issues:</strong></p><p>Level Up Llama Tech, an accessories company, needs a solution to efficiently manage their feedback and product reviews. The organization would like to analyze customer reviews, identify product images and provide actionable insights to improve customer satisfaction and product quality.</p><p><strong>Solutions:</strong></p><p>The organization has agreed to implement an AI-powered system operated under Microsoft Azure services. This system will identify and properly classify product images using image recognition and utilize sentiment analysis to understand customer satisfaction grading. With these solutions presented, Level Up Llama Tech can engage with customer needs while improving their product offerings.</p><p><strong>Ingredients:</strong></p><ul><li>Free Azure Account (With a created Resource Group)</li><li>Computer Vision Resource</li><li>Text Analytics Resource</li><li>A Blob Storage Account</li><li>Blob Storage Container</li></ul><p><strong><em>Let’s get started!!!!!!!!</em></strong></p><p>First, log into the Azure Account and Create a Resource.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*SOlaW7_tu4nrks0PQESwYg.png" /><figcaption>To get started, click on create a resource</figcaption></figure><p>In the search bar, find the computer vision service and create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*O6szyoebw5SDonzfN-IFcg.png" /><figcaption>In the resource search bar, type in “Computer vision” service. Once found, click on create Computer Vision.</figcaption></figure><p>Select a subscription and resource group (we have already have formatted resource group).</p><p>Select the closest region and create a name for the Computer Vision service. For pricing and cost savings, select the F0 feature.</p><p>Once selected, review and create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G4Ytp9F-C9XRDCNr2Rl4Fg.png" /><figcaption>We used the previous Subscription and Resource Group. We selected the current region we are located in and created a name for this computer vision resource service. For pricing purposes, we selected Free F0. Once finished, select Review and create.</figcaption></figure><p>Review the created Computer Vision service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/1*QPdpd99BkkyocJca07yTBA.png" /><figcaption>View the created resource.</figcaption></figure><p>Next we will create a Blob Storage Account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/286/1*BjflOVJPQh5UWmtLZpbM9g.png" /><figcaption>Head back to the services and search for Storage Accounts. Click on create.</figcaption></figure><p>Create the Blob account storage with the suggested defaults of the Region, Subscription and Resource Group.</p><p>The Primary service will be for Blob Storage. The Primary workload will be for Machine Learning and Artificial Intelligence.</p><p>Once created, Click on review and create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QM6VkVY6PZXS-MCTZSUFWg.png" /><figcaption>Choose the previous subscription, resource group, and region. Create a storage name for the blob storage account. The selected primary workload is Machine Learning and Artificial Intelligence. Once validated, create the storage account.</figcaption></figure><p>Review the created Blob storage account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*Cgpd7TcGJcG0MykK8OFFXQ.png" /><figcaption>Once created, view the blob storage account.</figcaption></figure><p>Next, We will need to create a container to store the images and reviews.</p><p>First go back to the storage account. Scroll down and find containers. At the top of the containers portion, click on containers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/1*5gy5qIvGQXt1Jq0rp-xojw.png" /><figcaption>Go to the blob account and scroll to containers. Click and create container.</figcaption></figure><p>Create a name for the container.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/1*rdK_it7tMCBvaMl74vtv3A.png" /><figcaption>Create a name for the container.</figcaption></figure><p>Once the container is created, we need to store the product images and customer reviews in the container.</p><p>Click on Upload to store those images and customer reviews.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RtW16QYO8zm0zPhyOeOt7Q.png" /><figcaption>You will upload both pre configured images and reviews.</figcaption></figure><p>Now, let’s head to the Computer Vision resource.</p><p>Scroll and Click on Vision Studio.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*20bSt_3hsv1RvulHE6SUdA.png" /><figcaption>Click on Vision Studio to start the Image Analysis.</figcaption></figure><p>Once you have entered Vision Studio, find “Detect Common Objects in Images” and select that feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/616/1*lV7ci11E6DAKEXbsIec7nw.png" /><figcaption>Select Common objects in images</figcaption></figure><p>Click choose a different resource and select the resource group you would like to use or create a new resource group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*91dII_HtmnAibZttC_0urg.png" /><figcaption>Select the resources provided.</figcaption></figure><p>You will now test out a few product images seen below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2vNLQEnOObmAtrCsPFoZKw.png" /><figcaption>Take note of what is found in one of the product image findings. This product image is found the computer mouse at 83.70% and Laptop at 70.90%</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B-VADViZ48kwAxY8SAusRQ.png" /><figcaption>This product was identified as possibly a Camera at 60%.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dQS-xUjRTI0Im0mEEkz31A.png" /><figcaption>this product was identified as a watch at 70.30%.</figcaption></figure><p>Next, we will utilize the Sentiment Analysis API to review customer reviews.</p><p>First scroll back the Azure portal to find the <a href="https://language.cognitive.azure.com/home">Language Studio — Microsoft Azure</a>.</p><p>It will require you to create a new Resource group for the Language service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*FvDU5cfNL5bse-y_-pr_nA.png" /><figcaption>Create a new resource group for the language service.</figcaption></figure><p>Once you select the created resource group, you will arrive at the Language Studio Portal.</p><p>Click on Classify Text.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K6gvdGPAr8KoMMDUdygpFA.png" /><figcaption>Click to classify text.</figcaption></figure><p>Then you will select the Analyze Sentiment and Mine Opinions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/277/1*OkuoNZZ0XeDBBRTZmukWWA.png" /></figure><p>From here, you can either import the text files or copy and paste to run the Text Analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7hyjjakZeaHZTNOYgni7OQ.png" /><figcaption>Import or Copy/Paste text to run analysis. Click on Run to view the results.</figcaption></figure><p>Click on the run.</p><p>You will see how the text sentiment is analyzed for each response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6zxX8MZzV87erBGDpfYHpA.png" /><figcaption>You can see how each response is provided with a sentiment rating of either Positive, Neutral or Negative.</figcaption></figure><p>Congratulations! You were able to help Level Up Llama Tech focus on utilizing Azure Cognitive Services to automate the analysis of customer feedback through Image Recognition and Sentiment Analysis. These solutions enables Level Up Llama Tech to manage their reviews more efficiently and enhance product quality based on customer feedback and improve overall customer satisfaction!</p><p>Thank you for taking the time to viewing these Azure AI Services. If you found this article helpful, please provide a follow to this medium page or send a clap to increase viewership. If you would like to get more tips and tricks of the cloud industry, please send an invite to my LinkedIn at <a href="https://www.linkedin.com/in/alhaji-bah/">Alhaji Bah | LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=759ac7d88469" width="1" height="1" alt=""><hr><p><a href="https://blog.devops.dev/transforming-customer-feedback-with-ai-leveraging-image-recognition-%EF%B8%8F-and-sentiment-analysis-759ac7d88469">Transforming Customer Feedback with AI: Leveraging Image Recognition🖼️ and Sentiment Analysis…</a> was originally published in <a href="https://blog.devops.dev/">DevOps.dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Azure: Secure Remote Access, Auto-Scaling, and Load Balancing for Unstoppable VM…]]></title>
            <link>https://blog.devops.dev/mastering-azure-secure-remote-access-auto-scaling-and-load-balancing-for-unstoppable-vm-eca297db76b9?source=rss-51c5cf2a7669------2</link>
            <guid isPermaLink="false">https://medium.com/p/eca297db76b9</guid>
            <category><![CDATA[autoscaling]]></category>
            <category><![CDATA[load-balancing]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[virtual-machine]]></category>
            <category><![CDATA[ssh]]></category>
            <dc:creator><![CDATA[Alhaji Bah]]></dc:creator>
            <pubDate>Sun, 08 Sep 2024 19:42:46 GMT</pubDate>
            <atom:updated>2024-09-17T18:53:12.867Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mastering Azure: Secure Remote Access, Auto-Scaling, and Load Balancing for Unstoppable VM Performance</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*gHMtBh2HK1U4uqJkBdiR1w.png" /></figure><p><strong><em>Issues:</em></strong></p><p>Level Up Corp is hosting Linux applications with at-least 100 Azure Virtual Machines (VMs). The IT team will need a secure, efficient, reliable tool for remote administration and troubleshooting that will minimize downtime and security risks. The Corporation will also need to provide availability and scalability of those applications.</p><p><strong><em>Solutions:</em></strong></p><p>The first solution for the secure remote administration will be implementing SSH (Secure Shell) for the Linux Virtual Machines. In order to allow SSH into the Virtual Machine, we will need to create a Network Security Group (NSG) to allow SSH access. The second solution will be to create Auto Scaling Groups to automatically adjust to the number of virtual machines based on the demand. The Load Balancer will distribute traffic evenly across the VMs, allowing availability and reliability. Some benefits for the solution include improved productivity with efficiency, enhanced security, cost savings, simplistic administration, scalability and high availability.</p><p><strong><em>Ingredients:</em></strong></p><ul><li><em>A Free Tier Azure Account</em></li><li><em>Linux Azure Virtual Machine</em></li><li><em>A Resource Group</em></li><li><em>Network Security Group</em></li><li><em>Remote Security Shell Access key (SSH)</em></li><li><em>Auto Scaling Group</em></li></ul><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>To begin, let’s first log into our Azure Account.</p><p>Once logged in, find Azure Virtual Machine and click on create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M1WvUJN3BNaqzY-7z8CXtg.png" /><figcaption>Log into Azure Free Tier Account. Find Virtual Machine Service, and create Azure Virtual Machine</figcaption></figure><p>Select the subscription provided. You will need to either select an existing resource group or create a new resource group. Select a Region, and give the Virtual Machine a name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*Sm2NGq208TtOydxv87dEuA.png" /><figcaption>Create a new Resource group if you haven’t already. Give the Virtual Machine a name, select the nearest region, and Image (We selected Ubuntu Server 24.04).</figcaption></figure><p>Select the Size for the Virtual Machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/731/1*IBUcjTXPrcwvIO0kqFXpXA.png" /><figcaption>For this demo, we are using a Standard 8 GiB memory (Remember to shut this off when you are finished with this service!!)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/1*DD2XBBBMiL28OkuHJ0dYmA.png" /><figcaption>We will create an SSH Public Key for the authentication type. Create an easy to remember username, and key-pair name. We are allowing public ports to enter our VM so click on Allow.</figcaption></figure><p>Leave the remaining setting and click on Review &amp; create. Wait for Validation to pass before creating the Virtual Machine.</p><p>Once created, go to the resource and view the created Virtual Machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RT2Ag3wO6Sshs1y4lWZqrQ.png" /><figcaption>View the created Virtual Machine.</figcaption></figure><p>Next, we we verify the Network Security Group (NSG).</p><p>Go to Networking and select Network setting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-HEKf_J28B2oa-puZeu3Ww.png" /><figcaption>Click on network setting and view the networking security group.</figcaption></figure><p>To create a new Inbound port rule, click on the create port rule and select Inbound rule.</p><p>From here, you leave the source and destination as “Any”. The destination port range, for example, will be port 22 (this could also be port 443 or 80 if we need http or https access). The Protocol will be “TCP”. You need also to provide a number for the priority between 100–999.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/575/1*mw4hmiEBBaO8sJZ_1URfgQ.png" /><figcaption>Create the inbound rules for the Virtual Machine here.</figcaption></figure><p>Let’s connect the into the Virtual Machine!</p><p>Click into the Virtual Machine and click on connect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/349/1*KpLhTRtbqBtWz-Djo1UjQQ.png" /><figcaption>You will click on the connect button and select connect.</figcaption></figure><p>We will use the Native SSH to connect into our Virtual Machine. You will follow the commands and copy them to into your local machine for connectivity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/385/1*x7zUtZIxqyWKxDkwqBfefg.png" /></figure><p>After the permissions for the SSH keys, you can access the Virtual Machine. We verified the name of the VM with the “whoami” command.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/1*SJ7TJ78pAr_fmLPy8TlVHA.png" /></figure><p>Finally, let’s establish an Auto Scaling Group!</p><p>In the search bar, type in Virtual Machine Scale Sets. Click on create a new set.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/451/1*e7b6oJ7P7H45clDPGdLEbQ.png" /><figcaption>You will find the VM scale sets and click on create.</figcaption></figure><p>You will select the previous Subscription and Resource group.</p><p>Enter a name for the VM scale set, select a Region and Image for the VM image (Same configuration as creating the Azure VM).</p><p>In the Scaling Mode, you will be selecting Autoscaling. In the scaling configuration, the initial instance count = 2 but the maximum amount = 4.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/579/1*LdUXQbC7M8cVYR4Yhg5Wrw.png" /></figure><p>The authentication type remains the same (SSH Public Key). We will use the existing keys already stored in Azure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/1*UKaUtGFsthfzJB08_u0W6A.png" /><figcaption>We are using the SSH keys already stored in Azure.</figcaption></figure><p>Once all have been selected, select Review and create.</p><p>Let’s review the created Virtual Machine Scale sets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/891/1*9WGzvCGEo5v_NKgVxPhoEQ.png" /></figure><p>We verified the Virtual Machines portion in the Azure portal to see the created VMs based on the scaling configurations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/891/1*_M_G7PWCUfIpRrhFnOaIbA.png" /><figcaption>You can see both the created VMs through the Virtual Machine Scale Sets.</figcaption></figure><p>Congratulations! Thank you for taking the time to seeing how to create a secure remote protocol, network security group, and Virtual Machine Scaling Set configuration. I hope you find this help in your DevOp Cloud journey. If you did find this article helpful in any way, please send a clap to this article or follow me for more tips and tricks inside the cloud industry at <a href="https://www.linkedin.com/in/alhaji-bah/">Alhaji Bah | LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eca297db76b9" width="1" height="1" alt=""><hr><p><a href="https://blog.devops.dev/mastering-azure-secure-remote-access-auto-scaling-and-load-balancing-for-unstoppable-vm-eca297db76b9">Mastering Azure: Secure Remote Access, Auto-Scaling, and Load Balancing for Unstoppable VM…</a> was originally published in <a href="https://blog.devops.dev/">DevOps.dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Blob Storage: How to Create a Microsoft Azure Blob Storage Solution ]]></title>
            <link>https://blog.devops.dev/blob-storage-how-to-create-a-microsoft-azure-blob-storage-solution-df70b70ea154?source=rss-51c5cf2a7669------2</link>
            <guid isPermaLink="false">https://medium.com/p/df70b70ea154</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[blob-storage]]></category>
            <category><![CDATA[cloud-storage]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Alhaji Bah]]></dc:creator>
            <pubDate>Sun, 01 Sep 2024 14:58:13 GMT</pubDate>
            <atom:updated>2024-09-02T17:41:56.321Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>A visual step by step guide on using MS Azure Blob Storage Solution to host a static website by Alhaji Bah</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lK0Jd2am_WD50LIc" /></figure><p><strong>Scenario:</strong></p><p>Level Up Bank is a progressive financial institution that provides digital banking services to their customers. Leaders within the financial organization have expressed concerns with their current website being hosted on a on-premise server, which has led to constraints, complexity and extreme costs. The decision was made to move their static website into a Microsoft Azure Blob storage account.</p><p><strong>What is Microsoft Blob Storage?</strong> Microsoft Blob Storage, which is a part of Azure Storage, is a service that offers large storage amounts of unstructured data. “Blob”, which stands for Binary Large Object, can serve as an absolute storing solution for massive amounts of data such as logs, images, videos, backups and documents. For information regarding Blob storage, please visit the Microsoft white-papers <a href="https://azure.microsoft.com/en-us/products/storage/blobs">here</a>!</p><p>This is an exciting move for Level Up Bank because of the many benefits that follow with this decision. A few examples of the benefits are: cost savings with hosting a static website compared to utilizing a on-premise server, improved scalability that can meet the demands of the traffic hitting the website, high availability and redundancy across multiple regions and reduced management overhead, which can reduce the amount of burden on the IT team.</p><p><strong>Ingredients:</strong></p><ul><li><em>Free Tier Microsoft Azure Account</em></li><li><em>A Microsoft Blob Storage Account</em></li><li><em>A New Resource Group</em></li><li><em>A New Azure Blob Container</em></li><li><em>Level Up Bank index.html file</em></li></ul><h3><em>Let’s get started!</em></h3><p>— — — — — — — — — — — — — —</p><p>First, let’s sign into our free Microsoft Azure Account.</p><p>Search and select Storage Accounts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/887/1*14Q7WhuJ3sAEpf17DySbQg.png" /><figcaption>First create the Microsoft Account. Then log into your Microsoft Free Tier Account and scroll down where you will see the Azure Services provided.</figcaption></figure><p>Next, we will click on create Storage Account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/467/1*jyQGavo4KMMqc50IGhw7yw.png" /></figure><p>We will leave the subscription as default. For the Resource group, we created a new resource group (be mindful for the naming conventions, we are using Alhaji_keys for future creation of resources).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/839/1*imWO77Hso1X3RUVf3qmqDw.png" /><figcaption>You can create a new resource group as seen above.</figcaption></figure><p>For the name of the Storage Account, we will use “levelupbank” naming convention.</p><p>For regions, we selected the closest region available. For simplicity, we have selected “other” as the primary workload.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/867/1*hKwBGVRWrJb8AjpX1765_Q.png" /><figcaption>Create a name for the Storage Account, provide the primary service and workload.</figcaption></figure><p>Select Standard for performance and Geo-redundant storage (GRS) for Redundancy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*qhYi454yN-u-VkikWyjNNA.png" /></figure><p>Select Review and Create to view the storage account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/419/1*G4vtAjvk7jQBJ7fuE5vuqQ.png" /></figure><p>You can see that both the storage account and the new resource group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*4V0FUVm9--_m9q59R7vbCQ.png" /><figcaption>Once created, go to the home screen and you will see both services created.</figcaption></figure><p>Click on the storage account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/266/1*JG6iYt7NCOLDAVUBm40IIA.png" /><figcaption>Click on the created storage account.</figcaption></figure><p>Head to properties and select Blob service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/113/1*lP7liojYI4X0jpXAtEhoSA.png" /><figcaption>Scroll down the Storage account and find the properties tab. Select Blob Service</figcaption></figure><p>Click on Containers and create a container to upload the index.html file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/533/1*4z1zPmr0QSHZAzi2cUOZ5Q.png" /><figcaption>You can find the +containers selection after you click on the containers portion.</figcaption></figure><p>Create a name for the container then click on create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*bj3Ua60YcYq5FHNPEnoQFA.png" /><figcaption>Creat a unique name for the continaer. You will use this container to store the index html file.</figcaption></figure><p>Click on the container and upload the index.html file from your local device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*Q8rGFNFuU7_fWbcecWgZ9Q.png" /><figcaption>Upload index html file here.</figcaption></figure><p>You will head back to overview and select Capabilities. You will select Static Website. From here, you will need a name for document and the error document. Once you create, it will provide both a primary and secondary endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*b6DKCsn1w6f6jjhGMUGaEg.png" /><figcaption>Find the capabilities tab, click to static website and create document for both index &amp; error pages.</figcaption></figure><p>Next, You will head to overview and select Configuration.</p><p>You will find the “Allow Blob anonymous access” and enable it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/292/1*53FFU0s3uVpt6iLHyZSE5w.png" /><figcaption>Find the configuration tab. Once found, enable Allow Blob anonymous access.</figcaption></figure><p>Let’s head back into the container where the index.html is held.</p><p>We will change the anonymous access level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-SAt8UDmoHWeUZviJ7Jiaw.png" /><figcaption>We will select Container and change the access level (anonymous read access for container and blobs).</figcaption></figure><p>Lastly, we will go into the created container and click on the object.</p><p>Find the URL and copy it to the domain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/435/1*ifze_GHn-AkA1o8EIRvxkg.png" /><figcaption>Go to the container, click on the object and copy the URL on your local device.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/1*IQDW1-ogZ7vkvdTodJGMag.png" /></figure><p>Congratulations! You have successfully completed the implementation of a static website using a Microsoft Blob Storage Account! <strong>Level Up Bank </strong>now has a scalable, highly available and cost savings static website that fits their organization needs! Well Done!</p><p>Thank you for taking the time to navigating Microsoft Azure with me, I hope you find this help in your DevOp Cloud journey. If you did find this article helpful in any way, please send a clap to this article or follow me for more tips and tricks inside the cloud industry at <a href="https://www.linkedin.com/in/alhaji-bah/">Alhaji Bah | LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df70b70ea154" width="1" height="1" alt=""><hr><p><a href="https://blog.devops.dev/blob-storage-how-to-create-a-microsoft-azure-blob-storage-solution-df70b70ea154">Blob Storage: How to Create a Microsoft Azure Blob Storage Solution 🚀</a> was originally published in <a href="https://blog.devops.dev/">DevOps.dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Extracting Valuable Data with Python]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blog.devops.dev/extracting-valuable-data-with-python-e5e080b12763?source=rss-51c5cf2a7669------2"><img src="https://cdn-images-1.medium.com/max/1200/0*pFEBQXSxANsgZ5yK.jpg" width="1200"></a></p><p class="medium-feed-snippet">What is Python?</p><p class="medium-feed-link"><a href="https://blog.devops.dev/extracting-valuable-data-with-python-e5e080b12763?source=rss-51c5cf2a7669------2">Continue reading on DevOps.dev »</a></p></div>]]></description>
            <link>https://blog.devops.dev/extracting-valuable-data-with-python-e5e080b12763?source=rss-51c5cf2a7669------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5e080b12763</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Alhaji Bah]]></dc:creator>
            <pubDate>Sun, 04 Aug 2024 23:50:16 GMT</pubDate>
            <atom:updated>2024-08-05T17:29:25.690Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Code to Cloud: Crafting a Robust CI/CD Pipeline with AWS CodePipeline ☁️]]></title>
            <link>https://blog.devops.dev/code-to-cloud-crafting-a-robust-ci-cd-pipeline-with-aws-codepipeline-%EF%B8%8F-0a5ec5c245ca?source=rss-51c5cf2a7669------2</link>
            <guid isPermaLink="false">https://medium.com/p/0a5ec5c245ca</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[s3]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Alhaji Bah]]></dc:creator>
            <pubDate>Fri, 19 Jul 2024 16:01:23 GMT</pubDate>
            <atom:updated>2024-07-22T17:54:57.979Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*Aotq7Nvk3XaRVC__c7yo8g.png" /></figure><p>Your team of brilliant developers have requested for you to find a way to automate the deployment of a website. The developers have tested their code manually and would like to establish an easier path in this process. You have been instructed to provide a static site URL for the developers and make certain changes necessary to the code through a GitHub repository to verify that the CI/CD pipeline is working…</p><p>Before we can start constructing this pipeline, we must first define a few acronyms that will be used in this project.</p><p><strong>What is CI/CD</strong>? Simply put, CI/CD stands for Continuous Integration and Continuous Delivery/Deployment. CI/CD helps the automation of integrating, testing and deploying of code. This ideology makes software development faster, promote agility and efficiency. The Continuous Integration (CI) is the idea of committing code to a shared repository (repo) frequently, which can allow automated tests to detect errors quickly and reduce integration problems. While the Continuous Delivery/Deployment (CD) process ensures that code is in a deployable state and will be conducted in a testing, staging and deployment preparation step before being released in a production environment. The benefit of distributing CI/CD is that you can expect fast delivery, great reliability and improved quality in your software development.</p><p><strong>What is GitHub?</strong> GitHub is a web-based interface that allows for real-time collaboration. This web interface allows developers to work on a single project simultaneously, which can reduce production time, track changes and reduce the risk of duplicating work. GitHub uses Git, a tool that allows developers and non-developers to use version control.</p><p><strong>What is AWS CodePipeline?</strong> AWS CodePipeline is designed to streamline the process of software releases by automating the phases in building, testing, and deploying applications. Known for its fully managed continuous integration and continuous delivery, CodePipeline makes it easy to deliver updates quickly and reliably. This service integrates well with other AWS services and the setup process is very user-friendly; can be organized based on the specific project requirements. Learn about AWS CodePipeline <a href="https://docs.aws.amazon.com/codepipeline/latest/userguide/welcome.html#:~:text=AWS%20CodePipeline%20is%20a%20continuous,release%20your%20software%20changes%20continuously.">here</a>!</p><blockquote>Please follow my visual step by step guide for creating a CI/CD pipeline using AWS CodePipeline for deploying a static website!</blockquote><p>Ingredients:</p><ul><li>A GitHub Account</li><li>S3 Bucket</li><li>CI/CD Pipeline using AWS CodePipeline</li><li>HTML code</li></ul><p>To start this project, we must first head to <strong>GitHub</strong> and create an Account.</p><p>Once created, create a new repository. Provide a name for the repo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/826/1*xTjtZM1JRknxQycIX7lYHw.png" /><figcaption>Creating our 1st repo</figcaption></figure><p>If you can, add a description to the repo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/751/1*9UuYiCQcGWMaloQ5MfN8lg.png" /><figcaption>Description for our Repo</figcaption></figure><p>Also, add a README file. The README file is great to add any supporting documentation relevant in this repo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/1*2TQr_YMu7c-sZKOKisvBWg.png" /><figcaption>Always Add a README file. It’s good practice in case you have any supporting documentation for the repo</figcaption></figure><p>Finish and create Repo.</p><p>Next, Upload an HTML file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*GuaA20BWbRvUCqJ6dqY0Vg.png" /><figcaption>Upload the HTML file.</figcaption></figure><p>For the simplicity of this project, we create everything in the Main Branch. Add a description to this file. Once finished, Select commit changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*bccR3btkAFJ8fQFzgkAKKQ.png" /><figcaption>Upload the HTML file and commit the changes (saves the changes)</figcaption></figure><p>Review that changes have been pushed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*shB5inJ61LbPE7tpA76ATg.png" /></figure><p>Let’s now set up an <strong>S3 </strong>bucket for<strong> Static Web Hosting</strong>.</p><p>Go to your AWS Free Tier account and find the <strong>S3</strong> service.</p><p>Click on Create bucket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/164/1*3xvN15AHoW2WymK_oocMGg.png" /><figcaption>Find the S3 service and create a bucket</figcaption></figure><p>Provide a unique name for the bucket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/367/1*h5zEY5GTtq4t_vLZMS25ng.png" /><figcaption>Name the bucket</figcaption></figure><p>Once confirmed, go ahead and add the HTML file in the bucket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/515/1*VzhyceEciswuyik-0ITEuA.png" /><figcaption>Upload the HTML file on the bucket.</figcaption></figure><p>Remember to unblock the block public access permissions. Once you get that access, create a bucket policy that will allow public access into the bucket. If you have any questions on creating a bucket policy or unblocking block public access, check out my medium article on creating an S3 bucket and host static websites <a href="https://medium.com/devops-dev/creating-an-s3-bucket-hosting-a-static-website-using-the-s3-bucket-77d8c95c294d">here</a>!</p><p>Once completed, let’s verify that the HTML can be hosted in our S3 bucket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Ce5InAnNgEUdBKeVdCH4cw.png" /><figcaption>You should see the HTML file hosted.</figcaption></figure><p>Next, we will head to <strong>CodePipeline</strong> and create our <strong>CI/CD Pipeline.</strong></p><p>Find <strong>CodePipeline</strong> and click Create Pipeline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*EKVVtA05-qHrFcntiYbiTQ.png" /></figure><p>Name your Pipeline. Select Superseded and select new service role. Leave everything else as default.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*AoKd1BTwr-Pnhw8waSHkDw.png" /></figure><p>In the source stage, we will connect our <strong>GitHub</strong> account.</p><p>Click on connect to <strong>GitHub</strong> Account. You should be able to use the name of your repo to get to the AWS connector screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*9kS-FOzmQCGX9ugj6T8vZw.png" /></figure><p>You will come across a <strong>GitHub</strong> connection hub. Create a name for this connection and click on Connect to<strong> GitHub</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/582/1*BDQ4LWxjoE1JsAk6-hKzkw.png" /></figure><p>Click on Install a new app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/557/1*uAivCOEhxjGIKk_CkLvoHA.png" /></figure><p>A new window will prompt you to install AWS Connector with your <strong>GitHub</strong> account. Click on your <strong>GitHub</strong> account to configure connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/1*GMOkj4inXosCjKomMXtcPg.png" /></figure><p>Once connected, add the name of your repo and main branch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/1*maGQAKpr20cLo8Y7VbVjjA.png" /></figure><p>Then, we can skip the build stage (which is optional).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/154/1*Cy5UJiL8XdexTldu0xzfIQ.png" /></figure><p>Let’s configure the created <strong>S3</strong> Bucket by choosing the deploy provider. Click on Extract files before deploying.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*XwY3P6pBpWsc82HBBBorlQ.png" /></figure><p>Once completed, click on Create Pipeline and view the pipeline created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/522/1*ZpiJVSHHZCXsrl7HwPZzng.png" /></figure><p>Head back to your <strong>S3</strong> Bucket previously created and verify that the <strong>GitHub</strong> Repo was successfully pushed into your <strong>S3 </strong>Bucket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/1*yz5zA_5mPeHJlbi1Hs4KhA.png" /><figcaption>View the ReadME.md file from the GitHub repo</figcaption></figure><p>Verify that the actions were successfully created by going to the Pipeline settings and selecting Execution history.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0EqlRuf1fZr6TVz6XfT_mg.png" /></figure><p>Let’s head back into your <strong>GitHub </strong>repo.</p><p>Now let’s make a small change in our code and attempt to push it to our <strong>S3</strong> bucket. Click on the edit button (it&#39;s a pencil looking figure).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*ZRbvwux8rZAzGzlAskxSMg.png" /></figure><p>The developers wanted to add “Keep Your Dreams Alive” in the code. Copy the format and add that into the code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*2GHZUDZTB0p8abMZ5pPKRQ.png" /></figure><p>Once added, you will be prompted to save the changes. Click on Commit changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/463/1*EYWQ3rFdZ8895kNmKUh1Bw.png" /></figure><p>Now, let’s view our created <strong>S3</strong> bucket. We can see that changes have been triggered. To verify we will need to view our static website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1tM0cRX_JsplY96stWGGaw.png" /><figcaption>Find the S3 bucket and click on the website HTML.</figcaption></figure><p>Find the object URL and post it on a website domain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/769/1*kJoS_tDAcShLZw-_DCBY4A.png" /></figure><p>Finally, verify that the changes have been pushed seen below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a_I1hRU8N7dvt51YYSABmA.png" /><figcaption>Confirmation that changes have been reflected.</figcaption></figure><blockquote>Your team of developers now have an more efficient way to make change their code repository! You created a simple CI/CD pipeline that integrated with both S3 and GitHub, Congratulations!</blockquote><p>Troubleshooting not mentioned in this project:</p><ul><li>Trigger Configuration. I received an error prompt when first creating my Pipeline stating “The trigger configuration for the source action is not valid. Make sure to choose one trigger configuration for each source action.” I researched various online sources from Stack Overflow to ChatGPT 4 as how to add this trigger to my source. A few tips I was given were as follows: Validate the source provider (checking out if GitHub, S3 were configured correctly), Review my Pipeline Definition (check to see if each source action has corresponding trigger configuration placed) and check the Trigger configuration (check if you properly configured the trigger for the source action). This was an issue that initially I could not understand because I could not create my pipeline until I understood what the issues were.</li><li>In my second attempt, I review all the steps again and was able to create my pipeline. I made my change to the code, and I investigated to see if my changes were pushed from GitHub to S3. After a few minutes, the changes were reflected. After careful remediation and troubleshooting, I determined that my issue was that I did not correctly set my trigger configuration. Luckily, I was able to see the changes in the code and was able to make my first CI/CD pipeline.</li></ul><p>Thank you for taking the time to viewing this project. If you found this article helpful, please provide a follow to this medium page or send a clap to increase viewership. If you would like to get more tips and tricks of the cloud industry, please send an invite to my LinkedIn at <a href="https://www.linkedin.com/in/alhaji-bah/">Alhaji Bah | LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0a5ec5c245ca" width="1" height="1" alt=""><hr><p><a href="https://blog.devops.dev/code-to-cloud-crafting-a-robust-ci-cd-pipeline-with-aws-codepipeline-%EF%B8%8F-0a5ec5c245ca">Code to Cloud: Crafting a Robust CI/CD Pipeline with AWS CodePipeline 🔡☁️</a> was originally published in <a href="https://blog.devops.dev/">DevOps.dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unleashing DynamoDB: A Guide to Secure Access with IAM Roles]]></title>
            <link>https://medium.com/@alhaji_8801/unleashing-dynamodb-a-guide-to-secure-access-with-iam-roles-cb6a7b6bd6bf?source=rss-51c5cf2a7669------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb6a7b6bd6bf</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[dynamodb]]></category>
            <category><![CDATA[iam-roles]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[nosql]]></category>
            <dc:creator><![CDATA[Alhaji Bah]]></dc:creator>
            <pubDate>Mon, 15 Jul 2024 15:21:16 GMT</pubDate>
            <atom:updated>2024-07-15T19:31:19.085Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*WulyXCDDJApP4zAAi5lmzw.png" /></figure><p>AWS DynamoDB is a fully managed NOSQL database that provides a fast, secure, scalable database. Known for being strong, powerful and flexible, this database integrates well with other AWS services. Another attribute that DynamoDB presents is its ability to event stream data and storage of inconsistent schema items, meaning this database can handle less structured data more efficiently than relational data models (These address query volumes and provided high performance queries for item storage). For more information on DynamoDB check out this AWS documentation here: <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Introduction.html">What is Amazon DynamoDB? — Amazon DynamoDB</a></p><p>Let’s Go Media INC., a media production and distribution company, is observing different options to managing and tracking down metadata, ratings and other relevant information. The organization decides to use AWS DynamoDB to help the organization store and manage their content data.</p><p>This DynamoDB table will be called “latest_Movie_releases” and will feature 10 of the latest movies releases with movie titles, genres, release dates and ratings (based on Rotten Tomatoes movie ratings). For security of the table, the organization will establish IAM roles that will give the minimum necessary permissions to read the “latest_Movie_releases” table. At the end, the organization will need to verify that the DynamoDB table can be scanned correctly and the IAM role permissions as working as intended providing security of the latest movie releases data.</p><blockquote>Please follow this visual demonstration how to create a DynamoDB table, create an IAM Role, attaching that role to an EC2 instance and verifying that the correct permissions are enabled.</blockquote><blockquote>First, go to your AWS free tier account and find DynamoDB.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/1*7SAjV0gln7Bee0b8bVWdyw.png" /></figure><blockquote>Click on create table.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/894/1*JVwuJ2r_0iM5ZqR94XsrTA.png" /></figure><blockquote>Create the latest_Movie_releases in the Table name. For the Partition Key, we will name this movieid. This will need a unique identifier for each movie created, this will be shown as we create the table.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/1*werYrbTB_HAYY63CLK2Vbw.png" /></figure><blockquote>Once the table is created, go to the Actions button and find create item. Click on create item, this is where we will start adding entries into our table!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Mryd6npTTeFFDUSl6F5Gg.png" /><figcaption>Click to the named DB. Inside of the DB, go to actions and click on create item.</figcaption></figure><blockquote>Each Attribute will need a separate name provided. We will need a title, genre, releaseDate and ratings attribute. To do that as shown, click on the add new attribute drop down and select either numbers (for our movieid or ratings key) or String (movie title, genre). The release date could be either a string or number.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tizkHvLPg7GCeBTVERQAqQ.png" /><figcaption>We will select the recent Bad Boys movie. We will need to include the title, genre, release date and rating for each movie. Create new attribute dropdown, setting the title, genre as strings. For ratings, select numbers.</figcaption></figure><blockquote>Before you create the item, view the JSON view. This will show the template in a JSON format. We will copy this template to create each movie in table.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/373/1*D0HzGGx8WFuBcbZfN1Zwmw.png" /><figcaption>Click on JSON to view the JSON template</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*xBI_CbzGJLgHAcImqNcuUw.png" /><figcaption>We will use this template for all ten movies</figcaption></figure><pre>{<br>  &quot;movieid&quot;: {<br>    &quot;N&quot;: &quot;101&quot;<br>  },<br>  &quot;genre&quot;: {<br>    &quot;S&quot;: &quot;Action/Comedy&quot;<br>  },<br>  &quot;rating&quot;: {<br>    &quot;N&quot;: &quot;64&quot;<br>  },<br>  &quot;releaseDate&quot;: {<br>    &quot;S&quot;: &quot;2024-07-08&quot;<br>  },<br>  &quot;title&quot;: {<br>    &quot;S&quot;: &quot;Bad Boys: Ride or Die&quot;<br>  }<br>}</pre><blockquote>Once you created the first item, use the template above to create the remaining movies and their attributes ⬇️</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PhDdNt7goMimtWjG0oP9WA.png" /><figcaption>Use that template to create all attributes</figcaption></figure><blockquote>Now, Let’s create an EC2 instance and add an IAM role attached.</blockquote><blockquote>We named the EC2 instance latest_movie_releases. We need to use the Amazon Linux 2 Image and create a t.2 micro for the instance type. We can create a .pem key for SSH purposes and leave the remaining settings on default ⬇️</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lRJj0fiRF1o5muvFgn4vrQ.png" /><figcaption>Create EC2 instance, select AMI image (Amazon Linux 2)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/1*r5_19k0wAUGvqFzZT3Rp8Q.png" /></figure><blockquote>Once the EC2 instance is created, Go to IAM, find roles then select create roles.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/346/1*M2ilPdp3oKi0S_SJK29Jcw.png" /><figcaption>Go to IAM, then Roles than Create role</figcaption></figure><blockquote>Select AWS Service.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*byM0KkT9dH1cPCHPW3eutA.png" /></figure><blockquote>We will be attaching this role to an EC2 instance so select EC2.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BafHfCOYc_j7UKgo6h0ggA.png" /><figcaption>Select EC2 service</figcaption></figure><blockquote>Now, we can provide what the role name is and description. We named this role DynamoDB_Read Access and provided a brief description.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aWhMjoSsWzsuNhHPavyaVw.png" /><figcaption>Create the Role details for the DynamoDB</figcaption></figure><blockquote>Save the new policy. Let’s go to our EC2 instance and attach that policy. Go to the Actions button, find security and click on Modify IAM Role.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gAfj4JMNpOAR6AZZndb7sQ.png" /><figcaption>Attach the Read Access permissions to the EC2 instance by going to security and selecting Modify IAM role.</figcaption></figure><blockquote>Find the new role and attach it to EC2 instance. Hit update IAM role when completed.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8GnMm1sqjzym3lS-WCB9_g.png" /><figcaption>Add the new role to the EC2 instance and select update.</figcaption></figure><blockquote>Let’s connect into our Virtual Machine. If you need help connecting to a Virtual machine, please read my medium article on how to connect SSH into an AWS EC2 instance here: <a href="https://medium.com/devops-dev/the-ssh-way-lets-create-a-secure-remote-admin-with-our-linux-ec2-instances-%EF%B8%8F-55acdf94ff6b">The SSH way: Lets create a secure remote admin with our Linux EC2 instances 🌫️🖥💻 | by Alhaji Bah | DevOps.dev (medium.com)</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qH-tkC10_lnhb0RAuoV9ZQ.png" /><figcaption>Let’s connect into our EC2 instance!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VG3NC4W38b_fsWgZWB3hEg.png" /><figcaption>Connected into EC2 instance</figcaption></figure><blockquote>Now, Let’s Scan our AWS DynamoDB table in our EC2 instance! To scan our DynamoDB table, use the command the <em>“aws dynamodb scan”</em> command seen below ⬇️</blockquote><pre>aws dynamodb scan --table-name (name of DB title here)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oWICbcNCfSu5GZwLStLfOA.png" /><figcaption>You should be able to scroll and view all the 10 movie releases and metadata attached.</figcaption></figure><blockquote>Lastly, we will need to verify the read access and validate that we cannot write an item to the DynamoDB table. We have selected the Monkey Man movie for example and inputted the<em> “aws dynamodb put-item — table-name latest_Movie_releases — item” </em>with the Monkey Man metadata</blockquote><pre>aws dynamodb put-item --table-name latest_Movie_releases --item &quot;{\&quot;movieid\&quot;: {\&quot;N\&quot;: \&quot;105\&quot;}, \&quot;title\&quot;: {\&quot;S\&quot;: \&quot;Monkey Man\&quot;}, \&quot;genre\&quot;: {\&quot;S\&quot;: \&quot;Action/\&quot;}, \&quot;releaseDate\&quot;: {\&quot;S\&quot;: \&quot;2024-04-05\&quot;}, \&quot;rating\&quot;: {\&quot;N\&quot;: \&quot;89\&quot;}}&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yhrFzv9lDNuF3tow_doaqA.png" /><figcaption>As seen, we are not authorized to make any changes as permissions have been verified.</figcaption></figure><p>Congratulations! You were able to create a DynamoDB Table, create an IAM role, attach the role and verify those permissions. Now, Let’s Go Media have the database solution to effectively store information securely for their media content platform.</p><p>Thank you for taking the time to navigating the AWS CLI with me, I hope you find this help in your cloud journey. If you did find this article helpful in any way, please send a clap to this article or follow me for more tips and tricks inside the cloud industry at <a href="https://www.linkedin.com/in/alhaji-bah/">Alhaji Bah | LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb6a7b6bd6bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Two-Tier Architecture with Joomla ☁]]></title>
            <link>https://blog.devops.dev/building-a-two-tier-architecture-with-joomla-4066477f52ce?source=rss-51c5cf2a7669------2</link>
            <guid isPermaLink="false">https://medium.com/p/4066477f52ce</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[joomla]]></category>
            <category><![CDATA[vpc]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Alhaji Bah]]></dc:creator>
            <pubDate>Mon, 01 Jul 2024 17:08:58 GMT</pubDate>
            <atom:updated>2024-07-03T16:10:15.766Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/493/1*7XnEri5ZVeCduhN2710wCg.png" /><figcaption>This architecture provides direct and fast communication.</figcaption></figure><h3>SCENARIO:</h3><p>Adventure Works, a private travel agency that organizes tours &amp; travel packages across the globe, is looking for an innovative digital strategy that can enhance their customer engagement and modernize their business operations.</p><h3>GOAL:</h3><p>Their plan is to deploy a new website utilizing Joomla as their content management system. This new website will serve as a central hub for all their travel services. Also, it will ensure security, scalability and high availability to meet the demands of their clients and handle increased traffic for certain offerings during peak seasons of the year.</p><p>In this step-by-step visual guide, we will work through how to create a simple Two-Tier Architecture with the Joomla application and understand the benefits of creating a dynamic user-friendly website for Adventure Works. (Note: the website will be named my-test-site).</p><h3>INGREDIENTS:</h3><ul><li>Custom VPC</li><li>4 subnets (2 Public, 2 Private)</li><li>2 Route Tables (Public and Private)</li><li>Internet Gateway (attach to VPC)</li><li>NAT Gateway</li><li>Configuring the NACLs (Security groups for Public Subnets)</li><li>EC2 Instance</li><li>Security Groups for EC2 Instance</li><li>RDS instance (Amazon Relational Database Service)</li><li>Joomla Application setup</li></ul><h3>Definitions to keep in mind:</h3><p><em>Joomla </em>is an open-sourced content management system that allows you to build web content and powerful online applications. With Joomla, you can essentially build online web stores, directories, membership sites, etc. Joomla is written in <a href="https://www.php.net/">PHP </a>for managing content in the web and can use MySQL database to store content.</p><p>A <em>Two-Tier Architecture</em> is a software architecture that splits an application into two main layers:</p><ul><li>The web tier provides the interface and the logic side that a user can interact within the application. This tier will handle HTTP requests and allows web servers (Apache) to host various applications like the Joomla application. Think of this layer as the presentation layer.</li><li>The database tier handles the data by fronting a database instance like MySQL. This tier deals with the data storage, retrieval and management of the RDS instance. With utilizing the Joomla application, Joomla application would run on its own web server and database with the content and data configured.</li></ul><h3>Step One: Create a custom VPC</h3><p>Go to VPC in your AWS free tier account and click on create VPC.</p><p>Select VPC only, enter name of VPC and CIDR range (10.0.0.0/16 was used).</p><p>Note: We are using the range of 10.0.0.0/16 because it is the appropriate private IP address range.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*7mWQ4HS4v6_CzynSVsrPzg.png" /><figcaption>Creating custom VPC.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_hPrGX6nAByF8dqcV1VxlA.png" /><figcaption>Once complete, you should see this green completion bar.</figcaption></figure><h3>Step Two: Creating our Public and Private Subnets</h3><p>After you create the VPC, click on the subnet portion underneath the VPC label and create subnet ⬇️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/255/1*hRBLZdD0qwf9WxcN0CMdYw.png" /></figure><p>Be sure to specify the name of each Subnet and CIDR Block Ranges. This will ensure that both the webserver and the database are on separate subnets, which will enhance security and organizational clarity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/1*zYHRRNZ6jaMslpwho1ab3A.png" /><figcaption>creating Subnets (4)</figcaption></figure><p>Keep in mind that because we are tasked to create 4 total subnets, two subnets (Public &amp; Private) will be placed in <em>us-east-1a </em>and the other two will be placed in<em> us-east-1b.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*KMMIuSONYQNf17Doc4_fYg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/1*_Tqmog6NRq1ZzIcCNFkLDg.png" /></figure><p>Once completed, view the creation of the subnets. You should see two different availability zones for all four subnets ⬇️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JRhKpPHB_T4pu3FTjw6WHQ.png" /></figure><h3>Step Three: Create the Internet Gateway and Attach it to VPC</h3><p>Next, you will create the Internet Gateway.</p><p>Click on Internet Gateway and name the IGW.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/1*wt8F0JrHCmjTyeHzNg0-pQ.png" /><figcaption>Creating Internet Gateway and attach to VPC</figcaption></figure><p>Once created, a green bar will appear that will allow you to attach the IGW.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/338/1*RaQMpfhKE_s_akzYq4BWfg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*Lz9uuL6HF-bBLbHBudmqgg.png" /></figure><h3>Step Four: Create the NAT Gateway</h3><p>Now, let’s create our NAT Gateway.</p><p>Name the NAT Gateway and select the subnet will be creating it under. Select the Connectivity type as Public then allocate the Elastic IP for the NAT Gateway.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*LARS4VnAEOtd32h-L_NJJA.png" /><figcaption>Creating NAT Gateway</figcaption></figure><h3>Step Five: Create Public and Private Route Tables</h3><p>Let’s click to routing tables and create our first routing table.</p><p>Name it Public (we named it public_rt) then attach it to the VPC.</p><p>Repeat the same exact process for creating your Private Routing table. (we named our private_rt).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/733/1*UMFGl82OnoaMkyqaC-44Iw.png" /><figcaption>You will see your VPC based on the naming convention</figcaption></figure><p>Once both routing tables are created, let’s edit the routes to have our Internet Gateway and NAT Gateway attached to our routing tables.</p><p>Go to the Public routing table, click on it, and select edit routes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C2aUipE-7jl8GN4XULwrJQ.png" /></figure><p>In the editing of the public route, add route. Once a new route is added, select 0.0.0.0/0 as the destination. Select Internet Gateway then attach the Internet Gateway that was created previously.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1005/1*DljRIACnn_abOEeMyaJfGg.png" /><figcaption>Public RT for IGW</figcaption></figure><p>The last part of the routing table will include associating the two public subnets to the public routing table. Click on the public routing table and select edit subnet associations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*irduFEjMYa6EN6GDq9KsKg.png" /><figcaption>Add Public Subnets to Public RT</figcaption></figure><p>Select the two public subnets and click on save.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IIzawUOdoXBaS8efqmTLbw.png" /></figure><p>Now you will edit the routes of the Private routing table. Select the private routing table and click on edit routes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-a81aNmbh-H40ybx5wqFTQ.png" /><figcaption>Now we edit routes and subnet associated with private subnets</figcaption></figure><p>Click on add route, select 0.0.0.0/0 as the destination and now we can add the NAT Gateway to the Private Routing table.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nc_6wvqup5KDSaK8gg1sBQ.png" /><figcaption>Add the Nat GW to private RT</figcaption></figure><p>Let’s go ahead and associate the private subnets to the private routing table. Click on the Private routing table and select subnet associations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3J_60KxwGoftDHRXSVP3kw.png" /></figure><p>Select the two private subnets and save.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QQfIKaOzha0ad9onCHQ_tg.png" /></figure><h3>Step Six: Configuring the Network Access Control List</h3><p>Almost done with establishing our VPC, let’s ensure we have the ports created to connect into our subnet.</p><p>Scroll to NACLs and click on the NACL ids with the 4 subnets associated with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X6dz3s2XfhoaA-CnArMFag.png" /><figcaption>Creating NACLs for our subnet</figcaption></figure><p>Click on edit inbound rules and add rules 22 (port 22), rules 80 (HTTP) and port 443 (encrypted communication) and save.</p><p>Go back to the NACL of the VPC.</p><p>Click on edit outbound rules. Add rules 22 (port 22) rules 80 (port 80) and 443 (port 443).</p><h3>Step Seven: Creating our Virtual Machine</h3><p>Find EC2 service and click on Launch Instance ⬇️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/297/1*DBYqlgoVvvJRLyZy5sNPqQ.png" /><figcaption>Creating our Virtual Machines</figcaption></figure><p>For simplicity, select the AWS Amazon Linux 2023 AMI Image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V6bUw88vZsbjZncz8odc4Q.png" /></figure><p>We will select t2.micro instance type and create a keypair (named 2tier)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*b7R82KkNgWNxV-m08nF5oA.png" /></figure><p>Let’s edit the network configuration! Click on edit then select the VPC we are using. From there, you will select the subnet that this instance will be under.</p><p>Select Enable to Auto-Assign Public IP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t3ihLNs-5P4Izxngqdd4_g.png" /></figure><p>We will create security groups with the inbound rules for port 22, port 80 and port 443. Once added port, finish the creation of EC2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aXpsv1BSzR-86QHpBH6MQg.png" /></figure><h3>Step Eight: Creating our RDS Instance</h3><p>Find the RDS service and click on create database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2H7b-2V6XUsMnhorlCD-2g.png" /><figcaption>Create RDS instance</figcaption></figure><p>Select Standard create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/583/1*YJQudxP8FucxVBe3s71zSQ.png" /></figure><p>Choose the MySQL engine type.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/616/1*ZH_zF_CSpEkkw-X5WuB5TQ.png" /></figure><p>Select the Free Tier (Yes, we love EVERYTHING FREE)!!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mqJzmxeVWxuH_yOnsvgFYw.png" /><figcaption>WE LOVE ANYTHING FREE</figcaption></figure><p>We will create a name for our Database (We named this my-db)</p><p>For the credentials setting, we named the Master Username as Admin and selected the self-managed portion to create our own password with our database instance. (It will be important to have the master username, password and DB endpoint once we configured and connect Joomla).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a1hfIiMddmtxhaDtsFItLQ.png" /><figcaption>Select the VPC where you want the Db instance attached too</figcaption></figure><p>Lastly, you will tie the VPC to the instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/224/1*hLYSpQOU2DD7KLtLtXcZTw.png" /></figure><p>Let’s ensure that the security groups connect to our DB instance.</p><p>Go to EC2, security groups, find the SG and add port 3306 to the inbound rules.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*seOPMpsbjJJn5OC-UkJYEA.png" /><figcaption>Edit Inbound rules for RDS instance.</figcaption></figure><p>For the web server outbound rules configured when creating our EC2 instance, add port 3306 and tie that webserver security group in the destination portion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6mPvHS2ciWYpKsoIo8cNuA.png" /><figcaption>Edit outbound rules in the Webserver Sg to allow 3306 (RDS)</figcaption></figure><h3>Step Nine: Let’s connect into our EC2 instance</h3><p>Select the EC2 instance and click on connect.</p><p>Copy the 400 “2tier.pem” command.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DSGnTH-FvTCoqmbvXYyV5Q.png" /><figcaption>Let’s connect to VM1/Public1</figcaption></figure><p>Go to your Computer’s command line. Change into the Downloads directory.</p><pre>cd Downloads</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*6YtlyfBLg6j6tVR8O-OFjQ.png" /></figure><p>Change the permission of your .pem file.</p><pre>chmod 400 (.pem file)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/805/1*Mx4nm8OLpaIIRYOAiDxqaA.png" /></figure><p>Once completed, let’s remote access into our EC2 instance.</p><pre>ssh -i &quot;.pem file&quot; ec2-user@ip address</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FJeGlHaBQkG1_O1ZyDRj2Q.png" /></figure><p>You should confirm yes and SSH into your EC2 instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*axiLzec0dVwu_KIFVK4wpA.png" /></figure><h3>Step Ten: Install Apache and Joomla</h3><p>After SSH into the EC2 instance, let’s go ahead and run the update command.</p><pre>sudo yum update -y</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*RHM_e2MyzOyTgk8QVHNf3w.png" /></figure><p>Now we can install Apache.</p><pre>sudo yum install httpd -y</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OW6ncK4wi0mnUhFbMS1D6Q.png" /><figcaption>Installing Apache</figcaption></figure><p>Once installed, let’s install Apache with the DB instance.</p><pre>sudo yum install httpd php php-mysqlnd php-fpm -y</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wtn_q3A-ujWgjyMkGkfbVA.png" /></figure><p>Alright, let’s start and enable the service.</p><pre>sudo systemctl start httpd<br>sudo systemctl enable httpd</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*hPADd20dGooBieOIddsPMA.png" /></figure><p>Now, we can install the Joomla application.</p><pre>wget https://downloads.joomla.org/cms/joomla3/3-9-28/Joomla_3-9-28-Stable-Full_Package.zip</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FmHV2nC-ENS23qWlovISNw.png" /><figcaption>Installing Joomla Application</figcaption></figure><p>After the Joomla application finishes installation, you must unzip the Joomla application file.</p><pre>sudo unzip Joomla_3-9-28-Stable-Full_Package.zip -d /var/www/html/</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XsqLuk0wos_hsGI1UA49Xw.png" /></figure><p>It will take a few moments to unzip. Once it unzips completely, let’s change both the ownership and permissions of the /var/www/html file path.</p><p>First, let&#39;s change the ownership.</p><pre>sudo chown -R apache:apache /var/www/html/</pre><p>Secondly, let’s now change the permissions.</p><pre>sudo chmod -R 755 /var/www/html/</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i_Q144wgPdwmEnRnJS6F1Q.png" /></figure><p>Lastly, let’s restart the webserver so it can catch and make all the necessary changes.</p><pre>sudo systemctl restart httpd</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*LhrWQax0aYBh8KWR1NcD3A.png" /></figure><h3>Step Eleven: Connecting our Public IPv4 instance with Joomla</h3><p>Now, let’s go back to our EC2 dashboard.</p><p>Copy the IPv4 address and paste it on a URL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Gmwj2D7Lmq3G-7tMivXKXg.png" /></figure><p>You will be brought into the Joomla user interface. You can create a sitename and description based on the usage of this website!</p><p>As for the Super User account, it is highly important to remember the credentials of the account. Try using an email address you are familiar with and an easy to remember username. Also, try creating an easy password to access this website as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*x4uOvAS_MGaYrW8XS2a1kw.png" /></figure><p>Next, you will move to Database configuration! You can name place the DB endpoint on the Host name.</p><p>The Username will be the master username of your DB Instance.</p><p>The password will be the created password when you first initiated your DB Instance (Please keep that information safe).</p><p>The database name is the same as the one you initiated your DB instance (We named ours my-db).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OpvDAKo6pK2PLA0aJEQOGw.png" /></figure><p>One of the final steps is deleting the installation setup. When you click on run Database this error will occur seen below ⬇️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OblsVdQ9kx2FHqK6Ob9J0A.png" /></figure><p>What you will need to do is go back into your computer terminal and SSH back into the EC2 instance.</p><p>From there, you should change directory into the installation setup file path.</p><pre>cd /var/www/html/installation</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/949/1*nejE8f3HPCqzLnAxTbg2Lg.png" /></figure><p>Use the sudo rm command to remove the txt file seen in the error prompt.</p><pre>sudo rm _Joomla().text</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8j_RLH4njaNyCcUaLKqoiw.png" /></figure><p>Once removed, use the “ls” command.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-kXiV7SnrTrCaO0An-VSJA.png" /></figure><p>Go back to the URL and typing in the IPv4 address once again.</p><p>Once entered you will come across an editing module page that will ask you to update and provide information out how to setup your Joomla application. (For testing purposes, we will only show a test page).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lARDnbczBCnSJJczxU8b8Q.png" /></figure><p>Once you enter Super username and Password, you should be able to access the public site seen below ⬇️⬇️⬇️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nJNijXZHE94MWuToxWDSYQ.png" /></figure><p>Congratulations! You have successfully created a Two Tier Application using Joomla. Adeventure Works now has the guidelines necessary to carry out their digital presence as a global travel agency!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*FM_A2phrt-JY5cBDWxVIFg.gif" /></figure><h3>Troubleshooting not shown in this project:</h3><p>This Project took a total of 5 total days to complete with 5 total attempts of creating this two-tier application. I ran into a few troubleshooting issues that need a few days to research what problems I ran into but nonetheless, challenged to find out what was wrong, and creating solutions.</p><p>First: I created subnets but didn’t place them in different Availability Zones. That would not create the high availability necessary for Adventure Works to scale their website out.</p><p>Second: I initially did not refer to the appropriate private IP address range specified by the Internet Assigned Numbers Authority (IANA). My third attempt I used the IPv4 address of 16.16.0.0/16, which would not be considered a private IP address space. This was a problem that took one of my brilliant cloud engineers to point out and get corrected.</p><p>Third: I struggled connecting into my subnet. I realized that I needed to create security groups within the subnet (Network Access Control List) to give me the ability to connect into my subnet. This took a couple of hours and research to realize what the issue was.</p><p>Fourth &amp; final: The full installation of Joomla. I realize I needed to first install Apache, update it with the DB instance then carry out the remaining parts of the installing Joomla. This troubleshooting did not take long to figure and get squared away.</p><p>Thank you for taking the time to viewing this project. If you found this article helpful, please provide a follow to this medium page or send a clap to increase viewership. If you would like to get more tips and tricks of the cloud industry, please send an invite to my LinkedIn at <a href="https://www.linkedin.com/in/alhaji-bah/">Alhaji Bah | LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4066477f52ce" width="1" height="1" alt=""><hr><p><a href="https://blog.devops.dev/building-a-two-tier-architecture-with-joomla-4066477f52ce">Building a Two-Tier Architecture with Joomla ☁🗄</a> was originally published in <a href="https://blog.devops.dev/">DevOps.dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>