<?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 Ed on Medium]]></title>
        <description><![CDATA[Stories by Ed on Medium]]></description>
        <link>https://medium.com/@c.esawmmal?source=rss-19bf5a7e39cf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*2Rd2oR8iFgRS9c2g</url>
            <title>Stories by Ed on Medium</title>
            <link>https://medium.com/@c.esawmmal?source=rss-19bf5a7e39cf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:29:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@c.esawmmal/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[Implementation of a set of EC2 instances using Terraform and AWS Systems Manager configuration with…]]></title>
            <link>https://medium.com/@c.esawmmal/implementation-of-a-set-of-ec2-instances-using-terraform-and-aws-systems-manager-configuration-with-5eb053bb8744?source=rss-19bf5a7e39cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/5eb053bb8744</guid>
            <dc:creator><![CDATA[Ed]]></dc:creator>
            <pubDate>Wed, 31 May 2023 03:40:31 GMT</pubDate>
            <atom:updated>2023-05-31T03:40:31.274Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Implementation of a set of EC2 instances using Terraform and AWS Systems Manager configuration with Amazon Simple Notification Service for automated installation of security officers.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7alweKvO7UPs4MmD.jpg" /></figure><p><strong>Project description:</strong></p><p>In this project based on a real-world scenario, I acted as DevSecOps Engineer, and I deployed a set of EC2 instances and infrastructure in an automated way using Terraform (infrastructure as code — IaC). Also, it was necessary to install a specific security agent on all these instances in an automated way.</p><p>Once I provisioned the infrastructure, AWS System Manager and its component Command Run were used to install the security agents in an automated way. I used the Amazon Simple Notification Service — SNS to send an email informing the whole process status.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-Vg4h6uKWdi88hOD.jpg" /></figure><p>Project Steps:</p><p><strong>Hands On Project — Part 1 — Terraform</strong></p><p>- Download and unzip Terraform files<br>https://tcb-bootcamps.s3.amazonaws.com/bootcamp-aws/en/terraform-mod5.zip</p><p>- Edit Terraform main.tf file using the VSCode:<br> — Change the VPC_ID and SUBNET_ID according to your default VPC</p><p>- Create SSH Key Pair<br> — name: sshkey1<br> — format: .pem</p><p>- Install Terraform on AWS Cloud Shell</p><p>sudo yum install -y yum-utils<br>sudo yum-config-manager — add-repo <a href="https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo">https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo</a><br>sudo yum -y install terraform</p><p>- Upload your edited terraform code to AWS Cloud Shell and unzip it</p><p>- Run terraform</p><p>$ terraform init<br>$ terraform plan<br>$ terraform apply</p><p>- Explore more about Terraform on <a href="https://learn.hashicorp.com/terraform">https://learn.hashicorp.com/terraform</a></p><p><strong>Hands On Project — Part 2 — AWS Systems Manager</strong></p><p>- Create an IAM role SystemsManagerToSNS</p><p>Policy: AmazonSNSFullAccess</p><p>- Create a Notification Topic DevOpsNotification | Copy the ARN</p><p>- Create a subscription — email:</p><p>- Run the System Manager Quick Setup<br> — Targets: choose instances manually</p><p>- Validate the ‘configuration’: “Success” status</p><p>- Explore the Session Manager connecting by SSH browser (please note: if the EC2 instances don’t show up, reboot both instances using the EC2 console to re-run the SSM-agent startup script)</p><p>- Execute “Run Command” to deploy the “security agent instalation”</p><p>— Command document: AWS-RunShellScript</p><p>— Command parameters:</p><p>sudo wget -q <a href="https://tcb-bootcamps.s3.amazonaws.com/bootcamp-aws/en/install_security_agent.sh">https://tcb-bootcamps.s3.amazonaws.com/bootcamp-aws/en/install_security_agent.sh</a> -P /tmp<br>sudo chmod +x /tmp/install_security_agent.sh<br>sudo /tmp/install_security_agent.sh<br>ls -ltr /usr/bin/security_agent</p><p>— Targets: choose instances manually</p><p>— Uncheck enable writing to S3 Bucket.</p><p>— Enable SNS Notification</p><p>IAM Role: SystemsManagertoSNS<br>SNS Topic: &lt;ARN&gt;</p><p>Events notifications: all Events</p><p>Change notifications</p><p>Notify me for: Per instance basis</p><p>- Open the AWS Cloud Shell and remove the resources created by Terraform</p><p>(If needed, re-install the Terraform following the same steps used previously)</p><p>cd terraform<br>./terraform destroy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5eb053bb8744" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CloudJourney#3: 
Implementation of a Scalable Web Application using the services of AWS Elastic…]]></title>
            <link>https://medium.com/@c.esawmmal/cloudjourney-3-implementation-of-a-scalable-web-application-using-the-services-of-aws-elastic-c7f49da877ae?source=rss-19bf5a7e39cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7f49da877ae</guid>
            <dc:creator><![CDATA[Ed]]></dc:creator>
            <pubDate>Tue, 09 May 2023 15:12:36 GMT</pubDate>
            <atom:updated>2023-05-09T15:12:36.588Z</atom:updated>
            <content:encoded><![CDATA[<p>CloudJourney#3: <br><em>Implementation of a Scalable Web Application using the services of AWS Elastic Beanstalk, DynamoDB, CloudFront and Edge Location</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vyyUmMJxKPSGow2Ns1FIsw.png" /></figure><p><strong>Project description:</strong></p><p>In this project based on a real-world scenario, I was responsible for implementing an application that needs to support the high demand of a large number of users accessing it simultaneously. This application has been used in a large conference that had more than 10,000 people, in-person and online, with participants from all over the world.</p><p>This event was broadcast online and in person and 10 vouchers were drawn for 3 Cloud certifications. At that moment, more than 10,000 people in the audience registered their e-mails to guarantee their participation in the raffle.</p><p>We used in AWS, Elastic Beanstalk services to deploy the web application, DynamoDB to store emails, CloudFront to cache static and dynamic files in an Edge Location close to the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fh-2rrUNSN2eMAFC2HaBsQ.png" /></figure><p>In this project, we implemented a scalable Python web application using AWS Elastic Beanstalk. AWS Elastic Beanstalk is a fully managed service that makes it easy to deploy and scale web applications and services. It takes care of provisioning the underlying infrastructure, load balancing, auto scaling, and application health monitoring.</p><p>We started by creating a new Elastic Beanstalk environment. We then selected Python as the language and NGINX as the web server. We also uploaded our Python application code to the environment.</p><p>Once our application code was uploaded, Elastic Beanstalk automatically deployed it to the environment. We then tested the application and confirmed that it was working correctly.</p><p>We then scaled our application up to 4 instances. We also configured Elastic Beanstalk to automatically scale our application up or down based on CPU utilization.</p><p>We then stress test the EC2 instance and validate auto scaling EC2 instances capability with Elastic Beanstalk. We were able to successfully deploy and scale our Python web application using AWS Elastic Beanstalk. Elastic Beanstalk made it easy to focus on our application code and not worry about the underlying infrastructure.</p><p>Benefits of using AWS Elastic Beanstalk</p><p>There are many benefits to using AWS Elastic Beanstalk for deploying and scaling web applications. Some of these benefits include:</p><ul><li>Ease of use: Elastic Beanstalk is a fully managed service, which means that AWS takes care of provisioning the underlying infrastructure, load balancing, auto scaling, and application health monitoring. This makes it easy to get started with deploying and scaling web applications.</li><li>Scalability: Elastic Beanstalk makes it easy to scale your web applications up or down based on traffic. This can help you save money on infrastructure costs when your application is not under heavy load.</li><li>Security: Elastic Beanstalk provides a secure environment for deploying and running your web applications. AWS takes care of patching and updating the underlying infrastructure, which helps to protect your application from security vulnerabilities.</li><li>Cost-effectiveness: Elastic Beanstalk is a cost-effective way to deploy and scale web applications. You only pay for the AWS resources that you use.</li></ul><p>If you are looking for a simple and cost-effective way to deploy and scale web applications, then AWS Elastic Beanstalk is a great option.</p><p>Project Implementation Steps: <br># Steps on DynamoDB</p><p>- Create a new table<br> — name: users<br> — primary key: email</p><p># Steps on Elastic Beanstalk</p><p>- Platform: Python 3.7+</p><p>- Application code:<br> — Upload your code: <a href="https://tcb-bootcamps.s3.amazonaws.com/bootcamp-aws/en/tcb-conf-app-EN.zip">https://tcb-bootcamps.s3.amazonaws.com/bootcamp-aws/en/tcb-conf-app-EN.zip</a></p><p>Click in ‘Configure more options’:</p><p>- Presets:<br> — Configuration presets: High availability</p><p>- Software:<br> — Environment properties:<br> — — AWS_REGION = us-east-1</p><p>- Instances:<br> — Root volume type: General Purpose SSD — 8 GB</p><p>- Capacity:<br> — Instances Min: 2<br> — Instances Max: 4<br> — Instance type: t2-micro<br> — Scaling triggers:<br> — — CPUUtilization<br> — — Unit: Percent<br> — — Period: 1 Min<br> — — Breach durantion: 1 Min<br> — — Upper threshold: 50<br> — — Lower threshold: 40</p><p>- Security:<br> — Select SSH key</p><p>- Networking:<br> — VPC: Default:<br> — Add IP Public<br> — Select all subnets</p><p>- Create App</p><p>- Once the deploy completes, access the application and simulate a record insertion</p><p>- Investigate the error in the logs</p><p>- Add the permission AmazonDynamoDBFullAccess on the EC2 associate role in IAM.</p><p>- Try to insert the registry once again. It should be sucessful.</p><p><strong>Hands-on Project Solution — Part 2</strong></p><p>- Create CloudFront distribution<br>- Allowed HTTP methods: GET, HEAD, OPTIONS, PUT, POST, PATCH, DELETE</p><p><strong>Hands-on Project Solution — Part 3</strong></p><p>Perform load testing.</p><p>- Install the stress tool to perform the load testing</p><p>sudo amazon-linux-extras install epel -y<br>sudo yum install stress -y</p><p>stress -c 4</p><p>- Explore the resources created by the AWS Elastic Beanstalk (EC2, ELB, Auto Scaling Group, Cloud Watch resources) and also the auto scaling process</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7f49da877ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Journey#2: Migration of a Workload running in a Corporate Data Center to AWS using the Amazon…]]></title>
            <link>https://medium.com/@c.esawmmal/cloud-journey-2-migration-of-a-workload-running-in-a-corporate-data-center-to-aws-using-the-amazon-de567b611403?source=rss-19bf5a7e39cf------2</link>
            <guid isPermaLink="false">https://medium.com/p/de567b611403</guid>
            <dc:creator><![CDATA[Ed]]></dc:creator>
            <pubDate>Thu, 04 May 2023 18:52:22 GMT</pubDate>
            <atom:updated>2023-05-09T15:16:16.190Z</atom:updated>
            <content:encoded><![CDATA[<h3><em>Cloud Journey#2: Migration of a Workload running in a Corporate Data Center to AWS using the Amazon EC2 and RDS service.</em></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MYrkt1lvCnZ1olMs3npi1w.png" /></figure><p>In another project based in a real-world scenario, I acted as the Cloud Specialist responsible for migrating a workload running in a Corporate DataCenter to AWS.<br> The application and database were migrated to AWS using the Lift &amp; Shift (rehost) model, moving both application and database data.</p><p>I followed some migration steps: Planning (sizing, prerequisites, resource naming), Execution (resource provisioning, best practices), Go-live (validation test — Dry-run, final migration — Cutover) and Post Go-live (ensure the operation of the application and user access).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Y_jNDDOvBs6UwkMYSFa2g.png" /></figure><p>We deployed a secure and compliant cloud environment to meet the needs of our growing business. We created a Virtual Private Cloud (VPC) in CIDR <a href="http://10.0.0.0/16">10.0.0.0/16</a> and three subnets: <a href="http://10.0.0.0/24">10.0.0.0/24</a>, <a href="http://10.0.0.1/24">10.0.0.1/24</a>, and <a href="http://10.0.0.2/24">10.0.0.2/24</a>. We attached an Internet Gateway to the VPC, configured a route table, and created a new security group to allow connectivity between the EC2 instance and the new RDS instance. This configuration ensures that our environment is secure and compliant with industry standards, while also providing the flexibility and scalability that our business needs to grow.</p><p><strong>Project Implementation Steps:</strong></p><p><strong># VPC Provisioning</strong></p><p>- Create a VPC:</p><p>- CIDR Block: 10.0.0.0/16<br>PS: It should NOT overlap with on-premises or other cloud providers</p><p>- VPC Name: vpc-production-1</p><p>- Public subnet details:</p><p>vpc-production-1-pu-1 (Public)<br>CIDR Block: 10.0.0.0/24</p><p>- Private subnet details:</p><p>vpc-production-1-pv-1 (Private)<br>CIDR Block: 10.0.1.0/24</p><p>vpc-production-1-pv-2 (Private)<br>CIDR Block: 10.0.2.0/24</p><p>- Creating an Internet Gateway, Attaching it to a VPC and Creating an Route</p><p>VPC | Internet Gateway: igw-mod3 | Action: Attach to VPC (vpc-production-1)<br>VPC | Route Table | Routes | Edit routes | Add route: 0.0.0.0/0 — Target: Internet Gateway (igw-mod3)</p><p><strong># EC2 Provisioning</strong></p><p>- Create a new EC2 instance</p><p>- Amazon Machine Image: Ubuntu 18.04<br>- Instance type: t2.micro<br>- Instance details:<br>- Network: vpc-production-1<br>- Subnet: vpc-production-1-pu-1 (Public)<br>- Assign public ip: Enable<br>- Tags:<br>- hostname: awsuse1app01<br>- environment: bootcamp<br>- Configure security group:<br>- Port: 22 — Source: 0.0.0.0/0<br>- Port: 8080 — Source: 0.0.0.0/0</p><p><strong># RDS Provisioning</strong></p><p>- Create a RDS instance</p><p>- MySQL<br>- MySQL 5.7.30<br>- Templates: free-tier<br>- Settings:<br>- DB Instance: awsuse1db01<br>- Master username: admin<br>- Master password: admin123456<br>- DB instance class: db.t2.micro<br>- Storage: 20 GB<br>- Connectivity:<br>- VPC: vpc-production-1<br>- Public access: No<br>- Create new VPC security group<br>- New VPC security group name: sec-group-db-01<br>- Availability Zone: us-east-1a</p><p><strong>Hands-on Project Solution — Part 2</strong></p><p># Pre-requisites steps to run in the EC2 instance (Application Server)</p><p>sudo apt-get update<br>sudo apt-get install python3-dev -y<br>sudo apt-get install libmysqlclient-dev -y<br>sudo apt-get install unzip -y<br>sudo apt-get install libpq-dev python-dev libxml2-dev libxslt1-dev libldap2-dev -y<br>sudo apt-get install libsasl2-dev libffi-dev -y</p><p>curl -O <a href="https://bootstrap.pypa.io/pip/3.6/get-pip.py">https://bootstrap.pypa.io/pip/3.6/get-pip.py</a> ; python3 get-pip.py — user</p><p>export PATH=$PATH:/home/ubuntu/.local/bin/</p><p>pip3 install flask<br>pip3 install wtforms<br>pip3 install flask_mysqldb<br>pip3 install passlib</p><p>sudo apt install awscli -y<br>sudo apt-get install mysql-client -y</p><p><strong>Hands-on Project Solution — Part 3</strong></p><p># Steps to run during the “dry-run &amp; cutover”:</p><p>- Open port RDS security group:</p><p>- Type: MySQL/Aurora<br>- Source: 0.0.0.0/0<br>(only for bootcamp purporses — in production env, you should open the ports to the application server IPs only)</p><p>- Connect to the EC2 instance</p><p>$ ssh ubuntu@&lt;PUBLIC_IP&gt; -i &lt;ssh_private_key&gt;</p><p>- Download the dump file and app file</p><p>wget <a href="https://tcb-bootcamps.s3.amazonaws.com/bootcamp-aws/en/wikiapp-en.zip">https://tcb-bootcamps.s3.amazonaws.com/bootcamp-aws/en/wikiapp-en.zip</a><br>wget <a href="https://tcb-bootcamps.s3.amazonaws.com/bootcamp-aws/en/dump-en.sql">https://tcb-bootcamps.s3.amazonaws.com/bootcamp-aws/en/dump-en.sql</a></p><p>- Connect on MySQL running on AWS RDS</p><p>mysql -h &lt;RDS_ENDPOINT&gt; -P 3306 -u admin -p</p><p>- Create the wiki DB and import data</p><p>create database wikidb;<br>use wikidb;<br>source dump-en.sql;</p><p>- Create the user wiki in the wikidb</p><p>CREATE USER wiki@’%’ IDENTIFIED BY ‘wiki123456’;</p><p>GRANT ALL PRIVILEGES ON wikidb.* TO wiki@’%’;</p><p>FLUSH PRIVILEGES;</p><p>- Unzip the app files</p><p>unzip wikiapp-en.zip<br>cd wikiapp</p><p>- Edit the wiki.py file and change the MYSQL_HOST and point to the RDS endpoint.</p><p>vi wiki.py</p><p>- Bring up the application</p><p>python3 wiki.py</p><p>Steps to validate the migration:</p><p>- Open the AWS console, copy the public IP and test the application using:</p><p>&lt;EC2_PUBLIC_IP&gt;:8080</p><p>- Login to the application :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de567b611403" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>