We are going to create a simple web app that tells the time. A simple html,css and js application that users can find out the current time with just a click of a button.
- we will be creating a launch template because we might want to attah our application with an auto-scaling group incase of failover.
- we will need an application load-balancer to help us direct and control traffic coming into to our application. we will need to edit the security group of our target group to direct traffic into our loadbalancer SG.
- Route 53 will also be needed as a domain registrar and a DNS A record.
Step 1: We launch a single instance with the launch template,the template consists of certain configurations such as security groups,key pair and all other configuration needed. After launching this single instance,we then test if wecan reach the app because we already configured the app in our luanch template using a custom ec2-data-script that can be found in this repo under the launch-template directory. Ensure that port 80(HTTP) is open because we are working with an apache web app.
Step 2: After testing our application and seeing it work we then move to creating a security group for our load balancer,a target group and an application load balancer. for the SG of the ALB, we will need to open port 80. so we can map it to the target group of our instances.
Step 3: We will not be adding any database yet,but we will see it in the next project. after creating the SG for the ALB,the target group and the ALB, we move forward to registering the instance into our newly created target group. after registering the instances,we go to the sg of that single instance and edit the inbound rule to only receive traffic from our alb SG. By doing this,we can only reach our aplication by the dns link of our load balancer and not wiith the public ip of our instances. The dns link looks like this: "http://demo-alb-663644520.us-east-1.elb.amazonaws.com".
Step 4: We create an auto scaling group with multiple availability zone enabled,this solves the problem of disaster recovery and also high-availability. while creating the ASG we attach our Application load-balancer to the ASG too.
Step 5: Creating Route53 domain registrar and DNS records (an A record to be precise because we want traffic to be routed to the public ip) for our application. also enabling the Alias type so dns queries will be directed to our ALB. The routing policy will be set to simple or latency, any of the two would be just fine. We create a public hosted zone because we are on a public network. The name will be "marvelloustime.com", then we create a dns record and it shoould be of type A and it should be attached to our existing load balancer and our routing policy set to simple. we will not attach any subdomain leaving it as "marvelloustime.com" with the alias setting turned on. NOTE: you must have purchased a domain registrar on aws for you to actually have your domain records work, i do not have the resources to purchase this domain just yet but will do when i have them. This is the end of this project thank your for reading.