create target groups demo added

Author: Jaime Salas Zancada

04-cloud/aws/09-elb/demos/02-user-data/readme.md

@@ -1,3 +1,98 @@
 # User Data
 
-Lets
+Lets start by creating a script that will install Docker on the instance type that we're using:
+
+Create `install-docker.txt`
+
+```bash
+#!/bin/bash
+sudo dnf update
+sudo dnf install docker -y
+sudo systemctl start docker
+sudo systemctl enable docker
+sudo usermod -aG docker $USER
+newgrp docker
+```
+
+If we want to start a new instance with user data we can do as follows:
+
+```bash
+aws ec2 run-instances --image-id <image id> --count 1 --instance-type <instance type> \
+--key-name my-key-pair --subnet-id <subnet id> --security-group-ids <sg-id> \
+--user-data file://my_script.txt
+```
+
+We're going to use the Ireland region and the default vpc and subnet. So lets try to grab the values that we need to do this:
+
+```bash
+VPC=$(aws ec2 describe-vpcs --region eu-west-1 | jq -r '.Vpcs[0]."VpcId"')
+```
+
+Lets also create a security that allows SSH Traffic
+
+```bash
+SSHSG=$(aws ec2 create-security-group \
+--group-name ssh-sg \
+--description "ssh-sg" \
+--region eu-west-1 \
+--vpc-id $VPC | jq -r '.GroupId')
+```
+
+```bash
+aws ec2 authorize-security-group-ingress \
+  --group-id $SSHSG \
+  --region eu-west-1 \
+  --ip-permissions '[{"IpProtocol":"tcp","FromPort": 22,"ToPort": 22,"IpRanges": [{"CidrIp":"0.0.0.0/0"}]}]'
+```
+
+For last we need a subnet on default VPC, lets grab one:
+
+```bash
+SUBNET=$(aws ec2 describe-subnets --filters "Name=vpc-id,Values=$VPC" \
+--region eu-west-1 | jq -r '.Subnets[0]."SubnetId"')
+```
+
+We need to create a key in order to access our new instance, go to dashboard and create `dublin_key`
+
+With this we're finally ready to try to start our instance with user data:
+
+> NOTE: We have taken the image id from region AMI Catalog
+
+```bash
+aws ec2 run-instances --image-id ami-07355fe79b493752d \
+ --count 1 --instance-type t3.micro \
+ --key-name dublin_key --subnet-id $SUBNET --security-group-ids $SSHSG \
+ --region eu-west-1 \
+--user-data file://install-docker.txt
+```
+
+Now lets conenct to instance:
+
+```bash
+ssh -i "dublin_key.pem" ec2-user@ec2-54-78-159-28.eu-west-1.compute.amazonaws.com
+```
+
+If we just simply run `docker` we will see the list of available commands. But if we try any command with out sudo, we will get an error. 
+
+```bash
+docker ps
+```
+
+We can check that docker is running, by checking the service status:
+
+```bash
+sudo systemctl status docker
+```
+
+The reason for that, is that the $USER during installation, is not the same one that we are using when we're connected via SSH, lets fix that:
+
+```bash
+sudo usermod -aG docker $USER
+newgrp docker
+```
+
+Now if we run `docker ps` everything looks good.
+
+## References
+
+- https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-data.html#user-data-shell-scripts

04-cloud/aws/09-elb/demos/03-web-tier-deploy/readme.md

@@ -0,0 +1,52 @@
+# Demo
+
+We're going to SSH into web1 and deploy the web front end using `Docker`. We're then going to browse directly to web1's public IP address and verify that the web front end is actually working. 
+
+- SSH into `web1`
+- Deploy the front end using Docker
+- Browse to web1's public IP address
+
+## Deploying the Web
+
+Now, just so you're not taken by surprise, let's look at the Docker command we're going to run. You don't need to understand this in any detail, but there are a couple of things I want to point out. 
+
+```bash
+sudo docker run -d \
+ -p 80:80 -p 443:443 \
+ -h web1 \
+ benpiper/mtwa:web
+```
+
+```bash
+docker run -d -p 80:3000 -h web1 jaimesalas/todo-app-front:4
+```
+
+Let's go ahead and SSH into the `web1` instance and run this. 
+
+- Connect to your instance
+
+```bash
+ssh -i "your_key" your_instance
+```
+
+Here we are on the `web1` instance, and the first thing we're going to do is spin up the Docker container for the web front end. So we're going to go ahead and enter the command for that. 
+
+```bash
+docker run -d -p 80:3000 -h web1 jaimesalas/todo-app-front:4
+```
+
+Let's go ahead and grab the instance's public IP address. We'll do a curl `ifconfig.me`.
+
+```bash
+curl ifconfig.me
+```
+
+Let's jump over to our browser and then paste the IP address into the address bar and hit Enter. 
+
+> Copy public IP on browser
+
+Now the front end of the web app is configured to display information about the client, web server, and application server. 
+
+Open dev tools, the cookie information is also blank because we, the client, have not sent any cookie.
+
+> Browse using `https://<your ip>`