Loading gists…
EC2
| 1 | tankey style ec2 banayune with ngnix pani |
| 2 | |
| 3 | HIGH-LEVEL ARCHITECTURE |
| 4 | VPC |
| 5 | ├── Public Subnet (EC2-1) |
| 6 | ├── Public Subnet (EC2-2) |
| 7 | ├── Internet Gateway |
| 8 | └── Route Table → Internet |
| 9 | ⚙️ STEP-BY-STEP (Algorithm Style) |
| 10 | 🔹 STEP 1: Create VPC |
| 11 | |
| 12 | Go to → VPC Dashboard |
| 13 | |
| 14 | Click Create VPC |
| 15 | Choose: |
| 16 | Name: MyVPC |
| 17 | CIDR: 10.0.0.0/16 |
| 18 | Create |
| 19 | |
| 20 | 👉 This is your private network |
| 21 | |
| 22 | 🔹 STEP 2: Create 2 Subnets |
| 23 | |
| 24 | Go to Subnets → Create subnet |
| 25 | |
| 26 | Subnet 1: |
| 27 | Name: Public-Subnet-1 |
| 28 | CIDR: 10.0.1.0/24 |
| 29 | AZ: any |
| 30 | Subnet 2: |
| 31 | Name: Public-Subnet-2 |
| 32 | CIDR: 10.0.2.0/24 |
| 33 | |
| 34 | 👉 Both are PUBLIC (we’ll configure next) |
| 35 | |
| 36 | 🔹 STEP 3: Create Internet Gateway |
| 37 | Go to Internet Gateways |
| 38 | Create → Name: MyIGW |
| 39 | Attach to your VPC |
| 40 | |
| 41 | 👉 Now your VPC can talk to internet |
| 42 | |
| 43 | 🔹 STEP 4: Create Route Table |
| 44 | Go to Route Tables → Create |
| 45 | Name: Public-RT |
| 46 | Attach to VPC |
| 47 | Add Route: |
| 48 | Destination: 0.0.0.0/0 |
| 49 | Target: Internet Gateway |
| 50 | |
| 51 | 👉 Means: "Send all internet traffic outside" |
| 52 | |
| 53 | 🔹 STEP 5: Associate Subnets |
| 54 | Open Route Table → Subnet Associations |
| 55 | Attach both subnets |
| 56 | |
| 57 | 👉 Now both subnets are PUBLIC |
| 58 | |
| 59 | 🔹 STEP 6: Enable Auto Public IP |
| 60 | |
| 61 | For each subnet: |
| 62 | |
| 63 | Edit settings → Enable Auto-assign public IP |
| 64 | |
| 65 | 👉 Without this, EC2 won’t get public IP |
| 66 | |
| 67 | 🔹 STEP 7: Create Security Group |
| 68 | |
| 69 | Go to EC2 → Security Groups |
| 70 | |
| 71 | Create: |
| 72 | |
| 73 | Name: Web-SG |
| 74 | Add rules: |
| 75 | SSH (22) → My IP |
| 76 | HTTP (80) → Anywhere |
| 77 | |
| 78 | 👉 Allows login + web access |
| 79 | |
| 80 | 🔹 STEP 8: Create Key Pair |
| 81 | |
| 82 | Go to EC2 → Key Pairs |
| 83 | |
| 84 | Name: my-key |
| 85 | Download .pem |
| 86 | |
| 87 | 👉 Needed for SSH |
| 88 | |
| 89 | 🔹 STEP 9: Launch EC2 Instance 1 |
| 90 | |
| 91 | Go to EC2 → Launch Instance |
| 92 | |
| 93 | Name: EC2-1 |
| 94 | AMI: Amazon Linux |
| 95 | Instance type: t2.micro |
| 96 | Key pair: my-key |
| 97 | Network: |
| 98 | VPC: MyVPC |
| 99 | Subnet: Public-Subnet-1 |
| 100 | Auto IP: Enabled |
| 101 | Security Group: Web-SG |
| 102 | |
| 103 | Launch |
| 104 | |
| 105 | 🔹 STEP 10: Launch EC2 Instance 2 |
| 106 | |
| 107 | Same as above but: |
| 108 | |
| 109 | Name: EC2-2 |
| 110 | Subnet: Public-Subnet-2 |
| 111 | 🔹 STEP 11: SSH into EC2 |
| 112 | |
| 113 | In terminal: |
| 114 | |
| 115 | chmod 400 my-key.pem |
| 116 | |
| 117 | ssh -i my-key.pem ec2-user@<PUBLIC-IP> |
| 118 | |
| 119 | 👉 Now you are inside your server |
| 120 | |
| 121 | 🌐 (OPTIONAL) STEP 12: Create Load Balancer |
| 122 | |
| 123 | Go to EC2 → Load Balancers |
| 124 | |
| 125 | Create Application Load Balancer |
| 126 | Choose: |
| 127 | Internet-facing |
| 128 | Select your VPC |
| 129 | Select both subnets |
| 130 | Create Target Group: |
| 131 | Add both EC2 instances |
| 132 | Attach to Load Balancer |
| 133 | |
| 134 | 👉 Now traffic is distributed between EC2-1 and EC2-2 |
| 135 | |
| 136 | 🧠 FINAL UNDERSTANDING |
| 137 | |
| 138 | You just built: |
| 139 | |
| 140 | VPC = network |
| 141 | Subnets = zones |
| 142 | IGW = internet access |
| 143 | Route table = traffic rules |
| 144 | SG = firewall |
| 145 | EC2 = servers |
| 146 | Load balancer = traffic distributor |
| 147 | |
| 148 | |
| 149 | When you install Nginx on EC2: |
| 150 | |
| 151 | It runs a web server on port 80 |
| 152 | When you open EC2 public IP → it serves default page |
| 153 | ⚙️ STEP 1: Launch EC2 Instances (already done) |
| 154 | |
| 155 | Make sure both: |
| 156 | |
| 157 | In public subnet |
| 158 | Have public IP |
| 159 | Security Group allows: |
| 160 | HTTP (80) |
| 161 | SSH (22) |
| 162 | 🔐 STEP 2: SSH into EC2-1 |
| 163 | ssh -i my-key.pem ec2-user@<EC2-1-PUBLIC-IP> |
| 164 | 📦 STEP 3: Install Nginx on EC2-1 |
| 165 | Amazon Linux: |
| 166 | sudo yum update -y |
| 167 | sudo yum install nginx -y |
| 168 | |
| 169 | Start service: |
| 170 | |
| 171 | sudo systemctl start nginx |
| 172 | sudo systemctl enable nginx |
| 173 | |
| 174 | Check status: |
| 175 | |
| 176 | systemctl status nginx |
| 177 | 🌐 STEP 4: Test EC2-1 |
| 178 | |
| 179 | Open browser: |
| 180 | |
| 181 | http://<EC2-1-PUBLIC-IP> |
| 182 | |
| 183 | 👉 You should see: Nginx Welcome Page |
| 184 | |
| 185 | 🔁 STEP 5: SSH into EC2-2 |
| 186 | ssh -i my-key.pem ec2-user@<EC2-2-PUBLIC-IP> |
| 187 | 📦 STEP 6: Install Nginx on EC2-2 |
| 188 | |
| 189 | Run same commands: |
| 190 | |
| 191 | sudo yum update -y |
| 192 | sudo yum install nginx -y |
| 193 | |
| 194 | sudo systemctl start nginx |
| 195 | sudo systemctl enable nginx |
| 196 | 🌐 STEP 7: Test EC2-2 |
| 197 | http://<EC2-2-PUBLIC-IP> |
| 198 | |
| 199 | 👉 You should see same Nginx page |
| 200 | |
| 201 | 🎨 (OPTIONAL) STEP 8: Customize each server (IMPORTANT for learning) |
| 202 | |
| 203 | On EC2-1: |
| 204 | |
| 205 | echo "Hello from EC2-1" | sudo tee /usr/share/nginx/html/index.html |
| 206 | |
| 207 | On EC2-2: |
| 208 | |
| 209 | echo "Hello from EC2-2" | sudo tee /usr/share/nginx/html/index.html |
| 210 | |
| 211 | Now: |
| 212 | |
| 213 | EC2-1 IP → shows “Hello from EC2-1” |
| 214 | EC2-2 IP → shows “Hello from EC2-2” |
| 215 | 🧠 WHAT IS HAPPENING |
| 216 | Nginx is listening on port 80 |
| 217 | EC2 public IP routes traffic to instance |
| 218 | Security Group allows HTTP traffic |
| 219 | Nginx responds with HTML page |
| 220 | ⚠️ COMMON MISTAKES |
| 221 | |
| 222 | ❌ No HTTP rule in Security Group → page not opening |
| 223 | ❌ Nginx not started → connection refused |
| 224 | ❌ Using private IP → won’t work |
| 225 | ❌ Wrong AMI commands (Amazon Linux vs Ubuntu) |
| 226 | |
| 227 | 🚀 NEXT LEVEL (important) |
| 228 | |
| 229 | Now you can upgrade this setup: |
| 230 | |
| 231 | 👉 Add Load Balancer so you don’t need to use IPs |
| 232 | 👉 Access both EC2 via single DNS |
| 233 | 👉 Enable auto failover |
| 234 | |
| 235 | |
| 236 | |
| 237 |