From 5741d61b5db6aefc78649dc13889c3134a69cbdf Mon Sep 17 00:00:00 2001 From: purple360 <64763854+purple360@users.noreply.github.com> Date: Wed, 19 Jul 2023 12:25:24 +0000 Subject: [PATCH 01/10] Update 0-use_a_private_key --- 0x0B-ssh/0-use_a_private_key | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0x0B-ssh/0-use_a_private_key b/0x0B-ssh/0-use_a_private_key index dfba400..5b4e82d 100755 --- a/0x0B-ssh/0-use_a_private_key +++ b/0x0B-ssh/0-use_a_private_key @@ -1,3 +1,3 @@ #!/usr/bin/env bash # Connecting to a server through a private key -ssh -i ~/.ssh/holberton ubuntu@35.231.33.237 +ssh -i ~/.ssh/alx ubuntu@35.231.33.237 From 6c06180ef9c9759215f96233eb0c060102bbb04b Mon Sep 17 00:00:00 2001 From: purple360 <64763854+purple360@users.noreply.github.com> Date: Wed, 19 Jul 2023 12:25:50 +0000 Subject: [PATCH 02/10] Update 1-create_ssh_key_pair --- 0x0B-ssh/1-create_ssh_key_pair | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0x0B-ssh/1-create_ssh_key_pair b/0x0B-ssh/1-create_ssh_key_pair index a244f09..10ea186 100755 --- a/0x0B-ssh/1-create_ssh_key_pair +++ b/0x0B-ssh/1-create_ssh_key_pair @@ -1,3 +1,3 @@ #!/usr/bin/env bash # Creates an RSA key pair -ssh-keygen -t rsa -f holberton -b 4096 -N betty +ssh-keygen -t rsa -f alx -b 4096 -N betty From 9eea6fea323949bbecd1fef05de49362807aa453 Mon Sep 17 00:00:00 2001 From: purple360 <64763854+purple360@users.noreply.github.com> Date: Wed, 19 Jul 2023 12:26:25 +0000 Subject: [PATCH 03/10] Update 2-ssh_config --- 0x0B-ssh/2-ssh_config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0x0B-ssh/2-ssh_config b/0x0B-ssh/2-ssh_config index 1173a3a..ecde357 100644 --- a/0x0B-ssh/2-ssh_config +++ b/0x0B-ssh/2-ssh_config @@ -52,5 +52,5 @@ Host * HashKnownHosts yes GSSAPIAuthentication yes GSSAPIDelegateCredentials no - IdentityFile ~/.ssh/holberton + IdentityFile ~/.ssh/alx PasswordAuthentication no From 4758c361391675e9a4fb83852c8e709db9b76fe6 Mon Sep 17 00:00:00 2001 From: purple360 <64763854+purple360@users.noreply.github.com> Date: Wed, 19 Jul 2023 12:36:53 +0000 Subject: [PATCH 04/10] Update 0-use_a_private_key --- 0x0B-ssh/0-use_a_private_key | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0x0B-ssh/0-use_a_private_key b/0x0B-ssh/0-use_a_private_key index 5b4e82d..4b6215b 100755 --- a/0x0B-ssh/0-use_a_private_key +++ b/0x0B-ssh/0-use_a_private_key @@ -1,3 +1,3 @@ #!/usr/bin/env bash # Connecting to a server through a private key -ssh -i ~/.ssh/alx ubuntu@35.231.33.237 +ssh -i ~/.ssh/school ubuntu@35.231.33.237 From a5f6a99cc268549914626bc3a2d52fca9a7892d3 Mon Sep 17 00:00:00 2001 From: purple360 <64763854+purple360@users.noreply.github.com> Date: Wed, 19 Jul 2023 12:42:52 +0000 Subject: [PATCH 05/10] Update 1-create_ssh_key_pair --- 0x0B-ssh/1-create_ssh_key_pair | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0x0B-ssh/1-create_ssh_key_pair b/0x0B-ssh/1-create_ssh_key_pair index 10ea186..695cc92 100755 --- a/0x0B-ssh/1-create_ssh_key_pair +++ b/0x0B-ssh/1-create_ssh_key_pair @@ -1,3 +1,3 @@ #!/usr/bin/env bash # Creates an RSA key pair -ssh-keygen -t rsa -f alx -b 4096 -N betty +ssh-keygen -t rsa -f school -b 4096 -N betty From 27d0b1679c4f57b9e70770dc416abb3ecb8d4543 Mon Sep 17 00:00:00 2001 From: purple360 <64763854+purple360@users.noreply.github.com> Date: Wed, 19 Jul 2023 12:43:53 +0000 Subject: [PATCH 06/10] Update 4-puppet_ssh_config.pp --- 0x0B-ssh/4-puppet_ssh_config.pp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/0x0B-ssh/4-puppet_ssh_config.pp b/0x0B-ssh/4-puppet_ssh_config.pp index 7d7dafd..e06030c 100644 --- a/0x0B-ssh/4-puppet_ssh_config.pp +++ b/0x0B-ssh/4-puppet_ssh_config.pp @@ -1,6 +1,6 @@ # Changes SSH config file exec { 'echo': path => 'usr/bin:/bin', - command => 'echo " IdentityFile ~/.ssh/holberton\n PasswordAuthentication no" >> /etc/ssh/ssh_config', + command => 'echo " IdentityFile ~/.ssh/school\n PasswordAuthentication no" >> /etc/ssh/ssh_config', returns => [0,1], -} \ No newline at end of file +} From b12c294e12bbe8ed10f5c1df08f75c9434dd9e44 Mon Sep 17 00:00:00 2001 From: purple360 <64763854+purple360@users.noreply.github.com> Date: Wed, 19 Jul 2023 13:03:02 +0000 Subject: [PATCH 07/10] Rename 1-block_all_incoming_traffic_but to 0-block_all_incoming_traffic_but --- ..._all_incoming_traffic_but => 0-block_all_incoming_traffic_but} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename 0x13-firewall/{1-block_all_incoming_traffic_but => 0-block_all_incoming_traffic_but} (100%) diff --git a/0x13-firewall/1-block_all_incoming_traffic_but b/0x13-firewall/0-block_all_incoming_traffic_but similarity index 100% rename from 0x13-firewall/1-block_all_incoming_traffic_but rename to 0x13-firewall/0-block_all_incoming_traffic_but From 1d9af3d6c5aced18160688496544faca871c4c27 Mon Sep 17 00:00:00 2001 From: purple360 <64763854+purple360@users.noreply.github.com> Date: Wed, 20 Sep 2023 23:36:50 +0000 Subject: [PATCH 08/10] Update README.md --- 0x19-postmortem/README.md | 44 ++++++++++++++++++++++++++++++++++++++- 1 file changed, 43 insertions(+), 1 deletion(-) diff --git a/0x19-postmortem/README.md b/0x19-postmortem/README.md index c1e500e..5efe5e4 100644 --- a/0x19-postmortem/README.md +++ b/0x19-postmortem/README.md @@ -1 +1,43 @@ -# Postmortem \ No newline at end of file +# Postmortem +Sample Postmortem: Outage Resolution + +##Issue Summary: + +Duration: +Start Time: September 15, 2023, 14:00 UTC +End Time: September 15, 2023, 17:30 UTC +Impact: +Service Affected: E-commerce Website +Users Affected: 80% of users experienced slow page loading and checkout failures. +##Root Cause: + +The root cause of the outage was an unexpected surge in traffic due to a flash sale event. Our load balancer's auto-scaling mechanism failed to respond adequately, causing server congestion. + +##Timeline: + +Detection Time: September 15, 2023, 14:15 UTC +Detected by automated monitoring alert for high server load. +Actions Taken: +Investigated server logs and identified increased traffic. +Assumed it was a DDoS attack initially. +Misleading Paths: +Focused on network security logs. +Engaged the security team unnecessarily. +Escalation: +Incident escalated to the DevOps team. +SREs involved due to the severity of the issue. +Resolution: +Scaled server capacity manually to accommodate traffic. +Implemented rate limiting to mitigate impact. +Regular updates were posted on the website to keep users informed. +Root Cause and Resolution: + +The issue was caused by a surge in genuine user traffic, not a DDoS attack. Our auto-scaling algorithm was not optimized to handle such rapid traffic spikes. To resolve it, we manually scaled up server capacity and adjusted the auto-scaling algorithm parameters to respond more effectively to sudden traffic surges. + +##Corrective and Preventative Measures: + +Optimize auto-scaling parameters for more dynamic scaling. +Implement more robust traffic monitoring and alerting systems. +Enhance communication protocols for cross-functional incident response. +Establish a post-incident review process to capture lessons learned. +This outage highlighted the importance of continuously improving our infrastructure's scalability and incident response capabilities. We are committed to implementing these measures to ensure uninterrupted service for our users. From f6ad783893908ba51b45395dce4db18ea3d550b8 Mon Sep 17 00:00:00 2001 From: purple360 <64763854+purple360@users.noreply.github.com> Date: Wed, 20 Sep 2023 23:38:07 +0000 Subject: [PATCH 09/10] Update README.md --- 0x19-postmortem/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/0x19-postmortem/README.md b/0x19-postmortem/README.md index 5efe5e4..e6539f6 100644 --- a/0x19-postmortem/README.md +++ b/0x19-postmortem/README.md @@ -1,7 +1,7 @@ # Postmortem Sample Postmortem: Outage Resolution -##Issue Summary: +## Issue Summary: Duration: Start Time: September 15, 2023, 14:00 UTC @@ -13,7 +13,7 @@ Users Affected: 80% of users experienced slow page loading and checkout failures The root cause of the outage was an unexpected surge in traffic due to a flash sale event. Our load balancer's auto-scaling mechanism failed to respond adequately, causing server congestion. -##Timeline: +## Timeline: Detection Time: September 15, 2023, 14:15 UTC Detected by automated monitoring alert for high server load. @@ -34,7 +34,7 @@ Root Cause and Resolution: The issue was caused by a surge in genuine user traffic, not a DDoS attack. Our auto-scaling algorithm was not optimized to handle such rapid traffic spikes. To resolve it, we manually scaled up server capacity and adjusted the auto-scaling algorithm parameters to respond more effectively to sudden traffic surges. -##Corrective and Preventative Measures: +## Corrective and Preventative Measures: Optimize auto-scaling parameters for more dynamic scaling. Implement more robust traffic monitoring and alerting systems. From 19a75388076ab2a28ffaa4eb2285006611f2a714 Mon Sep 17 00:00:00 2001 From: purple360 <64763854+purple360@users.noreply.github.com> Date: Wed, 20 Sep 2023 23:51:01 +0000 Subject: [PATCH 10/10] Create 0-blog_post --- .../0-blog_post | 54 +++++++++++++++++++ 1 file changed, 54 insertions(+) create mode 100644 0x11-what_happens_when_your_type_google_com_in_your_browser_and_press_enter/0-blog_post diff --git a/0x11-what_happens_when_your_type_google_com_in_your_browser_and_press_enter/0-blog_post b/0x11-what_happens_when_your_type_google_com_in_your_browser_and_press_enter/0-blog_post new file mode 100644 index 0000000..d98274f --- /dev/null +++ b/0x11-what_happens_when_your_type_google_com_in_your_browser_and_press_enter/0-blog_post @@ -0,0 +1,54 @@ + +**Demystifying the Journey of a Web Request: What Happens When You Type "https://www.google.com" in Your Browser** + +*Introduction:* + +The seamless experience of browsing the web often conceals the intricate processes happening behind the scenes. When you type "https://www.google.com" into your browser's address bar and hit Enter, it triggers a fascinating journey involving various components of the web stack. In this article, we will unravel this journey, step by step, shedding light on the magic that brings your favorite websites to your screen. + +**Step 1: DNS Request:** + +Before your browser can connect to Google's servers, it needs to find out where they are located. This is where the Domain Name System (DNS) comes into play. When you hit Enter, your computer sends a DNS request to a DNS server, asking for the IP address associated with "www.google.com." This server may cache the IP or query other DNS servers to find the answer. + +**Step 2: TCP/IP Connection:** + +Once your computer knows where to find Google's servers, it initiates a TCP/IP connection to the provided IP address. This connection involves a three-way handshake, where both your computer and Google's servers exchange information to establish a reliable connection. + +**Step 3: Firewall Security:** + +As the connection is established, it passes through your computer's firewall. Firewalls are like security guards, monitoring and filtering incoming and outgoing traffic. They ensure that only safe and authorized data can flow in and out of your computer. + +**Step 4: HTTPS/SSL Encryption:** + +Security is paramount on the web, especially when transmitting sensitive data. Google uses HTTPS (Hypertext Transfer Protocol Secure) to encrypt the data exchanged between your browser and its servers. During the SSL (Secure Sockets Layer) handshake, a secure connection is established, safeguarding your information from prying eyes. + +**Step 5: Load-Balancer:** + +Google serves millions of users worldwide, and to manage this load efficiently, they employ load balancers. These smart devices distribute incoming traffic across multiple servers, ensuring optimal performance, redundancy, and high availability. + +**Step 6: Web Server:** + +The web server is where the real action happens. It receives your request and responds by sending back the web page you requested. Google uses powerful web servers like Apache or Nginx to handle these requests with lightning speed. + +**Step 7: Application Server:** + +Not all content on the web is static. Dynamic websites, like Google, rely on application servers to generate content on the fly. These servers process your request, execute scripts, and fetch data from databases or other sources to create the web page you see. + +**Step 8: Database Interaction:** + +Behind the scenes, Google relies on extensive databases to provide search results, personalized recommendations, and more. The application server communicates with these databases to fetch relevant information, ensuring that you receive the most up-to-date content. + +**Conclusion:** + +The journey of a web request, from DNS resolution to database interaction, involves a symphony of components working in harmony. Each plays a vital role in delivering a seamless browsing experience. Understanding these processes can deepen our appreciation for the technology that powers the web. + +**Share Your Insights:** + +Do you have any questions or insights about the inner workings of the web stack? Feel free to share them in the comments below! + +**Share the URL:** + +Read the full article on Medium: [Link to Your Blog Post] + +--- + +This sample blog post provides a simplified explanation of what happens when you type "https://www.google.com" in your browser. You can expand on each step with more technical details and examples to create a more in-depth article.