m346/KN05/x_res/custom-vpc.md

## Challenge B)

### Create VPC
Name: **M346-XXX-VPC**<br>
IPv4 CIDR Block: **10.0.0.0/16**<br>

### Create Public Subnets

Name: **M346-XXX-Public-1A**<br> 
Availability Zone: **us-east-1a**<br>
IPv4 CIDR Block: **10.0.1.0/24**

Name: **M346-XXX-Public-1B**<br>
Availability Zone: **us-east-1b**<br>
IPv4 CIDR Block: **10.0.2.0/24**

Name: **M346-XXX-Private-1A**<br>
Availability Zone: **us-east-1a**<br>
IPv4 CIDR Block: **10.0.3.0/24**

Name: **M346-XXX-Private-1B**<br>
Availability Zone: **us-east-1b**<br>
IPv4 CIDR Block: **10.0.4.0/24**

### Public route table (Main)
Beim Erstellen der VPC wird diese automatisch erzeugt. Es muss einfach folgendes Feld ergänzt werden:<br>
Name: **M346-XXX-Public-RT**<br>

### Create private route table

Name: **M346-XXX-Private-RT**<br>
VPC: **M346-XXX-VPC**<br>
Subnet associations: **Private-1A**, **Private-1B**

### Create Internet Gateway

Name: **M346-XXX-IGW**
VPC: **M346-XXX-VPC**

<br><br>


## Challenge C)

### Security Group for Instance in the Public-Subnet (Web-Access)
Name: **M346-XXX-Web-Access**<br>
Inbound Rules: **SSH** / **HTTP**

### Security Group for Instance in the Private-Subnet (Private-only)
Name: **M346-XXX-Priv-Only**<br>
Inbound Rules: **SSH** (Optional) / **ICMP** (für Ping)