Skip to content

Commit 0ac6111

Browse files
ajay-dhangarajay-dhangar
committed
added new docs for devOps
1 parent 74e7fb1 commit 0ac6111

File tree

6 files changed

+594
-0
lines changed

6 files changed

+594
-0
lines changed

‎absolute-beginners/devops-beginner/aws/_category_.json‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
{
2+
"label": "AWS",
3+
"position": 7,
4+
"link": {
5+
"type": "generated-index",
6+
"title": "AWS Cloud Practitioner Guide",
7+
"description": "Master the fundamentals of Amazon Web Services (AWS). This track is designed specifically for absolute beginners to understand cloud infrastructure, core services, and industrial security practices used at CodeHarborHub."
8+
},
9+
"customProps": {
10+
"icon": "☁️",
11+
"status": "new",
12+
"author": "CodeHarborHub Team"
13+
}
14+
}

‎absolute-beginners/devops-beginner/aws/core-services.mdx‎

Lines changed: 100 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,100 @@
1+
---
2+
title: "AWS Core Services"
3+
sidebar_label: "3. Core Services"
4+
sidebar_position: 3
5+
description: "A deep dive into the essential AWS services every developer needs to know. Learn about EC2, S3, RDS, and more. Understand how these services interact to build scalable applications on AWS."
6+
tags: [aws, core-services, compute, storage, database, networking]
7+
---
8+
9+
AWS offers hundreds of services, but as a **Full-Stack Developer** at **CodeHarborHub**, you only need to master the "Core 5" to build 90% of modern applications. We categorize these into **Compute**, **Storage**, **Database**, and **Networking**.
10+
11+
## 1. Compute Services: The Brains
12+
13+
Compute services provide the processing power for your applications. Whether you're running a Node.js API or a Python script, these services host your code.
14+
15+
### EC2 (Elastic Compute Cloud)
16+
EC2 provides resizable virtual servers. It is the most flexible compute option.
17+
18+
* **Instance Types:** Optimized for different tasks (e.g., `t3.micro` for testing, `c5` for heavy computation).
19+
* **AMIs (Amazon Machine Images):** Pre-configured templates (Ubuntu, Amazon Linux, Windows).
20+
21+
### Lambda (Serverless)
22+
Run code without provisioning or managing servers. You only pay for the milliseconds your code executes.
23+
24+
```mermaid
25+
graph LR
26+
A[Trigger: S3 Upload] --> B{AWS Lambda}
27+
B --> C[Process Image]
28+
B --> D[Update Database]
29+
C --> E[Final Output]
30+
```
31+
32+
If your application has unpredictable traffic or you want to avoid server management, Lambda is a great choice. For a MERN stack app, you might use Lambda for background tasks like image processing or sending emails.
33+
34+
## 2. Storage Services: The Memory
35+
36+
Where do your files, images, and backups live? AWS provides highly durable storage solutions.
37+
38+
<Tabs>
39+
<TabItem value="s3" label="Amazon S3 (Object)" default>
40+
41+
**Simple Storage Service (S3)**
42+
43+
* **Concept:** Store files as "Objects" in "Buckets."
44+
* **Durability:** 99.999999999% (11 nines). Your data is practically impossible to lose.
45+
* **Use Case:** Static website hosting, user profile pictures, logs.
46+
47+
</TabItem>
48+
<TabItem value="ebs" label="Amazon EBS (Block)">
49+
50+
**Elastic Block Store (EBS)**
51+
52+
* **Concept:** A virtual hard drive attached to an EC2 instance.
53+
* **Use Case:** Installing a database or an OS on a server.
54+
* **Scope:** Stays within a single Availability Zone.
55+
56+
</TabItem>
57+
58+
</Tabs>
59+
60+
## 3. Database Services: The Heart
61+
62+
Managing databases manually is hard. AWS RDS handles the heavy lifting like backups, patching, and scaling.
63+
64+
| Service | Type | Use Case |
65+
| :--- | :--- | :--- |
66+
| **Amazon RDS** | Relational (SQL) | Structured data, MySQL, PostgreSQL. |
67+
| **DynamoDB** | NoSQL (Key-Value) | High-speed, serverless, great for MERN apps. |
68+
| **ElastiCache** | In-Memory | Caching data for ultra-fast performance (Redis). |
69+
70+
## Service Interaction Map
71+
72+
Here is how a typical **CodeHarborHub** industrial-level architecture looks using these core services:
73+
74+
```mermaid
75+
flowchart TD
76+
User((User)) --> CloudFront[CloudFront - CDN]
77+
CloudFront --> S3[S3 - Static React App]
78+
User --> ALB[Application Load Balancer]
79+
ALB --> EC2[EC2 - Node.js Backend]
80+
EC2 --> RDS[(RDS - PostgreSQL)]
81+
EC2 --> S3_Files[S3 - User Uploads]
82+
```
83+
84+
In this architecture:
85+
* The user accesses the React frontend hosted on S3 via CloudFront for low latency.
86+
* The backend API runs on EC2 instances behind an Application Load Balancer (ALB)
87+
* The backend interacts with RDS for structured data and S3 for file storage.
88+
89+
## Quick Summary Table
90+
91+
| Service | Analogy | Why it's "Industrial Level"? |
92+
| :--- | :--- | :--- |
93+
| **EC2** | Your Laptop in the Cloud | Full control over the environment. |
94+
| **S3** | Unlimited Dropbox | Scales to petabytes of data effortlessly. |
95+
| **RDS** | A DBA in a Box | Automated backups and high availability. |
96+
| **VPC** | Your Private Office | Isolates your resources from the public internet. |
97+
98+
:::tip Developer Note
99+
If you are building a **MERN Stack** project, start with **EC2** for your Express server and **MongoDB Atlas** (or AWS DocumentDB). As you grow, move your frontend to **S3 + CloudFront** for global speed!
100+
:::

‎absolute-beginners/devops-beginner/aws/deploy-first-instance.mdx‎

Lines changed: 138 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,138 @@
1+
---
2+
title: "Deploy Your First Instance"
3+
sidebar_label: "5. Hands-on Lab"
4+
sidebar_position: 5
5+
description: "A step-by-step guide to launching, securing, and connecting to your first AWS EC2 Linux server. Learn the essential commands to prepare your server for a MERN stack deployment and understand the best practices for managing your cloud resources."
6+
---
7+
8+
Welcome to the final capstone of the **CodeHarborHub** AWS Beginner series! Today, you will move from theory to practice by launching a live **Ubuntu Linux** server in the AWS Cloud.
9+
10+
:::info Why This Matters
11+
Deploying your own server is a critical milestone in your DevOps journey. It gives you hands-on experience with cloud infrastructure, security, and server management. This lab will prepare you for real-world scenarios where you'll need to deploy and manage applications in the cloud.
12+
:::
13+
14+
## The Deployment Lifecycle
15+
16+
Before we click the buttons, let's look at what happens behind the scenes when you request a server.
17+
18+
```mermaid
19+
sequenceDiagram
20+
participant U as You (Developer)
21+
participant C as AWS Console
22+
participant R as EC2 Resource
23+
participant N as VPC/Network
24+
25+
U->>C: Select AMI & Instance Type
26+
C->>R: Provision Virtual Hardware
27+
R->>N: Attach Elastic Network Interface
28+
N->>R: Assign Public IP
29+
R->>R: Status Check (Initialising)
30+
R-->>U: Instance Running ✅
31+
```
32+
33+
In this lifecycle:
34+
1. You select the **AMI** (Amazon Machine Image) and **Instance Type** (virtual hardware).
35+
2. AWS provisions the virtual server and attaches it to the network.
36+
3. The server undergoes status checks to ensure it's healthy before you can connect.
37+
38+
## Step-by-Step Implementation
39+
40+
Follow these steps carefully. At **CodeHarborHub**, we use the **Free Tier** to ensure you learn without incurring costs.
41+
42+
### 1. Launch the Instance
43+
44+
1. Log in to the [AWS Management Console](https://aws.amazon.com/console/).
45+
2. In the search bar, type **EC2** and select it.
46+
3. Click the orange **"Launch instance"** button.
47+
48+
### 2. Name and Application Image (AMI)
49+
50+
* **Name:** `CodeHarborHub-Web-Server`
51+
* **AMI:** Select **Ubuntu** (Choose the `Ubuntu Server 24.04 LTS` - Free tier eligible).
52+
53+
### 3. Instance Type & Key Pair
54+
55+
* **Instance Type:** Select `t2.micro` (1 vCPU, 1 GiB Memory).
56+
* **Key pair:** Click **"Create new key pair"**.
57+
* **Name:** `codeharbor-key`
58+
* **Format:** `.pem` (for OpenSSH/Mac/Linux) or `.ppk` (for PuTTY/Windows).
59+
* **Action:** Download and save this file safely! **You cannot download it again.**
60+
61+
### 4. Network Settings (Security Groups)
62+
63+
The Security Group acts as a virtual firewall.
64+
65+
* **Allow SSH traffic from:** Anywhere (0.0.0.0/0) — *For production, use "My IP".*
66+
* **Allow HTTPS traffic** (Port 443).
67+
* **Allow HTTP traffic** (Port 80).
68+
* **Review and Launch** your instance.
69+
70+
## Connecting to Your Server
71+
72+
Once the instance state says **"Running"**, it's time to log in via your terminal.
73+
74+
<Tabs>
75+
<TabItem value="linux-mac" label="Linux / macOS" default>
76+
77+
1. Open your terminal and navigate to the folder containing your `.pem` file.
78+
2. Set permissions (Security requirement):
79+
```bash
80+
chmod 400 codeharbor-key.pem
81+
```
82+
3. Connect using the Public IP:
83+
```bash
84+
ssh -i "codeharbor-key.pem" ubuntu@<YOUR_PUBLIC_IP>
85+
```
86+
87+
</TabItem>
88+
<TabItem value="windows" label="Windows (PowerShell)">
89+
90+
1. Open PowerShell as Administrator.
91+
2. Navigate to your key folder and run:
92+
```powershell
93+
ssh -i .\codeharbor-key.pem ubuntu@<YOUR_PUBLIC_IP>
94+
```
95+
96+
*(Note: Modern Windows 10/11 has OpenSSH built-in\!)*
97+
98+
</TabItem>
99+
</Tabs>
100+
101+
## Industrial Level Commands
102+
103+
Once you are inside your server, run these commands to prepare it for a **MERN Stack** deployment:
104+
105+
```bash
106+
# Update the package manager
107+
sudo apt update && sudo apt upgrade -y
108+
109+
# Install Node.js (Current LTS)
110+
curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
111+
sudo apt-get install -y nodejs
112+
113+
# Verify installation
114+
node -v
115+
```
116+
117+
:::info Best Practice
118+
119+
Always keep your server updated to patch security vulnerabilities. Use `sudo apt update && sudo apt upgrade -y` regularly to maintain a secure environment.
120+
121+
:::
122+
123+
124+
## The "Wallet Safety" Rule
125+
126+
To keep your AWS account free, you must manage your resources. At the end of your practice session:
127+
128+
1. Go to the **Instances** dashboard.
129+
2. Select your instance.
130+
3. Click **Instance state** -> **Terminate instance**.
131+
132+
:::danger Warning
133+
**Stopping** an instance saves the data but might still charge for EBS storage. **Terminating** deletes the instance and stops all billing for that resource.
134+
:::
135+
136+
## Graduation Challenge
137+
138+
Now that your server is running, try to install **Nginx** (`sudo apt install nginx`) and paste your instance's **Public IP** into a browser. If you see the "Welcome to nginx!" page, you have successfully deployed a web server to the cloud!

‎absolute-beginners/devops-beginner/aws/global-infrastructure.mdx‎

Lines changed: 95 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,95 @@
1+
---
2+
title: "AWS Global Infrastructure"
3+
sidebar_label: "2. Global Infrastructure"
4+
sidebar_position: 2
5+
description: "Understand how AWS Regions, Availability Zones, and Edge Locations work to provide high availability. Learn the core concepts of AWS's global footprint and how to choose the right region for your applications."
6+
---
7+
8+
To build "Industrial Level" applications at **CodeHarborHub**, you must understand where your code actually lives. AWS doesn't just have "one big cloud"; it has a massive, physical footprint across every continent.
9+
10+
The AWS Global Infrastructure is built around three core concepts: **Regions**, **Availability Zones (AZs)**, and **Edge Locations**.
11+
12+
## The Infrastructure Hierarchy
13+
14+
Visualizing the relationship between these components is key to passing the **AWS Cloud Practitioner** exam and building resilient systems.
15+
16+
```mermaid
17+
graph TD
18+
A[AWS Global Cloud] --> B[Region: ap-south-1 Mumbai]
19+
A --> C[Region: us-east-1 N. Virginia]
20+
21+
subgraph "Inside a Region (e.g., Mumbai)"
22+
B --> D[AZ: ap-south-1a]
23+
B --> E[AZ: ap-south-1b]
24+
B --> F[AZ: ap-south-1c]
25+
end
26+
27+
subgraph "Inside an Availability Zone"
28+
D --> G[Data Center 1]
29+
D --> H[Data Center 2]
30+
end
31+
```
32+
33+
## 1. Regions
34+
35+
A **Region** is a physical location in the world where AWS clusters data centers.
36+
37+
:::info Key Fact
38+
Each Region is completely independent and isolated from other regions. This achieves the greatest possible fault tolerance and stability.
39+
:::
40+
41+
### How to Choose a Region?
42+
43+
When deploying your project (like a **MERN stack** app), consider these four factors:
44+
45+
1. **Compliance:** Does the data need to stay in India (e.g., for government projects)?
46+
2. **Latency:** How close is the region to your users? (e.g., Choose Mumbai for users in **Madhya Pradesh**).
47+
3. **Pricing:** Some regions (like US-East) are cheaper than others (like Sao Paulo).
48+
4. **Service Availability:** Not all AWS services are available in every region.
49+
50+
## 2. Availability Zones (AZs)
51+
52+
An **Availability Zone** consists of one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region.
53+
54+
| Feature | Description |
55+
| :--- | :--- |
56+
| **Isolation** | AZs are physically separated by miles to prevent "single point of failure." |
57+
| **Connectivity** | Connected via ultra-fast, low-latency private fiber-optic networking. |
58+
| **High Availability** | If one AZ goes down (flood/fire), your app fails over to another AZ. |
59+
60+
## 3. Edge Locations & CloudFront
61+
62+
**Edge Locations** are specialized data centers located in major cities globally. They are used by **Amazon CloudFront** (a Content Delivery Network) to deliver content to end-users with lower latency.
63+
64+
```mermaid
65+
sequenceDiagram
66+
participant U as User (Indore, India)
67+
participant E as Edge Location (Mumbai)
68+
participant O as Origin Server (US-East-1)
69+
70+
U->>E: Request codeharborhub.png
71+
Note over E: Is it in Cache?
72+
E-->>U: Yes! (Fast Delivery)
73+
Note right of E: No? Fetch from Origin
74+
E->>O: Request from US
75+
O->>E: Send File
76+
E->>U: Deliver to User & Cache
77+
```
78+
79+
## Comparison Summary
80+
81+
To help you remember for your interviews, here is the "CodeHarborHub Cheat Sheet":
82+
83+
| Component | Physical Scale | Primary Purpose |
84+
| :--- | :--- | :--- |
85+
| **Region** | Large (Cluster of AZs) | Data Sovereignty & Latency. |
86+
| **AZ** | Medium (Data Center) | High Availability & Disaster Recovery. |
87+
| **Edge Location** | Small (Cache Point) | Content Delivery Speed (CDN). |
88+
89+
## Hands-on Tip: Selecting a Region
90+
91+
When you log into your **AWS Management Console**, look at the top right corner. You will see a dropdown menu (e.g., "N. Virginia").
92+
93+
:::warning Important
94+
Always check your region **before** creating resources! If you create an EC2 instance in "Oregon" but your database is in "Mumbai," your application will be incredibly slow due to high latency.
95+
:::

0 commit comments

Comments
 (0)