Let's assumed you have requested your ACM, so in other words, you've got already your SSL for your domain name and you've got the domain name ready too with Route53.
Let's start deploying an EC2 instance and let it ready with the microservices and frontend we need, for the purpose of this example the instance was set it up with a Centos7 with a service which autostarts the backend Java services and with Nginx as the one is going to be running the front end plus a Reverse Proxy. once you've restarted that instance and it starts without any trouble starting up the whole services, so let's create an Image of that instance.
we are going to be
1 Creating a Classic load balancer
2: Creating a Launch Template
3: Creating an Auto Scaling Group
let's start creating a classic load balancer
Select your security group
Choose your certificate from ACM, for this purpose that process was done before about requesting the ACM certificate
Now pay attention to step 5, we have not selected in there any instance to start with, so that it is going to be managed with an Auto Scale group starting from a launch template
After you have created the load balancer, you've got to make an alias from the domain name to the Load Balancer, so go to Route53 - DNS Management - Hosted zones and select your domain name, click on Create Record Set, click on Alias YES, click on Alias Target and pick up the Load Balancer name you gave and click on Create
now the domain name is pointing to the Load Balancer
now let's go to AUTO SCALING - Launch Configurations and click on My AMIs and select the AMI I create before
I have chosen a t2.micro for the purpose of the example
I have chosen Create Auto Scaling Group after the Launch template was created, the path to go there is EC2 - AUTO SCALING - Launch Configurations, just select your template and create the auto-scaling group in there
I have given a name to the AutoScaling group, I have added the subnets, and pay attention to the one important thing, I have clicked on Receive traffic from one or more load balancers, so when I did that it immediately allowed me to attach the available load balancers to it, the Health Check Grace Period is by default 300 seconds, I changed by 150
in some seconds you will see the instances being deployed on the EC2 - Instances
making this short if you delete one instance of the maximum instance, it will automatically start a new one, if the instances are getting to the average CPU utilization, it will start a new instance automatically and if the instances are not being used, it starts turning down the instances.
Java Api and Frontend to test it
Comments
Post a Comment