Excellent, no fluff, clear explanation WITH solution diagram so we can visualize the end goal workflow.Thanks for sharing this easy to follow tutorial.
I love your channel man. Good explanations of concepts with practical demonstrations and I leave after 20-30 minutes knowing how to do something. Your videos are worth a lot more views than they get.
I haven't watched the whole video. But topology explanation and steps involved to create an autoscaling group were clearly articulated. That is a big thumb up from me. Believe me, there are a lot of ec2 auto scaling videos out there, but none provides the whole picture from the topology point of view. Well, done.
Hi Venkat, Bro HIghly appreciated your efforts, Many peoples get benefited by watching your tutorials. Without excepted anything you’re making efforts really speechless bro. Once again I would like to say Thanks a lot Bro.
Hi Kumar, Thanks for watching this video and taking time to comment/appreciate. It gives me immense pleasure in sharing my knowledge with others. Cheers.
Hi Venkat, We are waiting for your AWS videos like Route53, S3, ELB, EBS, EC2[ this is very huge topic we want more depth experience on this EC2] and still more VPC practical things like Transit gateway and examples and, You are videos are amazing with clear explanation. Hope you will release your AWS videos asap, and this is the good time to scale up my skills on AWS. Requesting you to kindly do more and more on AWS asap. May God bless you Venkat.
Hi, thanks for your interest in this channel. I will be doing more videos in this series. Currently my focus has shifted to Google Cloud and keeping on top of my Kubernetes series. But will continue this one as well whenever I get some time. Cheers.
Hi Mayank, thanks for watching. If you get 503, then your web application is not running on the ec2 instances. First test this setup without load balancer and make it work so that you can access the web application. Then introduce the loadbalancer.
@@justmeandopensource Actually it was my fault i attched another target grp to it. Thanks man for such an amazing vdo, i was trying this for whole day yesterdayyy. Stay blessed bro!
Sir, I am facing an issue in security groups. When I allowed default route and try to access EC2 instance using SSH it works, but when I use my IP as a source in security group and try to access the instance using ssh, it doesn't work. Please tell me how to figure it out?
This configuration is good for static content but what about dynamic changes which is frequently done in daily basis on instance level. WordPress based content are daily changes in /var/www/html/website/folder. how ASG work with that one ?
Hi Joseph, thanks for watching. There is a launch configuration which the Auto scaling group uses to launch similar instances. Basically everything is baked inside the image itself. So all instances launched by ASG will be identical.
Hi Anoop, AWS doesn't care whether your applications are stateful or stateless. You have a launch configuration that specifies how to launch the instance and you have auto scaling group that uses this launch configuration. ASG maintains the required number of instances based on scaling policies you define. Thats all AWS does. You will have to make sure how the instances manage the data. You either bake the data within the AMI or use EFS or external NFS for storing data persistently. Cheers.
Hi Venkat, Very nice topic thank you. I have implemented route53 with single ec2 instance. I haven't tried with route53 with autoscaling. If you have plan to release this topic in your future video id be happy to wait.
Hi Hareesh, thanks for watching this video. There are lots of topics I have got that are yet to be recorded. I will add this when it comes to Route53 concepts. Thanks for suggesting this topic. Cheers.
Can an ELB Classic (CLB) distribute traffic to two different Auto Scaling Groups, both running the same applications? (i.e. Kubernetes Masters in different AZs)
Is user data is mandate at the time of creating instance or I can install webserver once the instance is created. Have faced a issue while doing the lab error '502' .
Hi Yashwanth, thanks for watching. Userdata field is there just for automation. And it gets executed when the instance is launched. You can always run the commands later after instance started if you don't want to use user data.
@@justmeandopensource Thank you for answering my query. I am facing error 502 , showing instance health status as unhealthy and new instance are coming up . But this was going into loop. No actual output observed . Completely lost my weekend to achieve still no luck.
@@yashwanth4786 I think the health check is failing. The load balancer will route traffic only to the ec2 instances that are healthy. For some reason they don't seem to be healthy. So your web application might not be running properly. Just launch a separate ec2 instance from the ami and see if the web server is running.
@@justmeandopensource i have tried to access nginx default page on general instance. Am not able to access same O/P when the instances were under auto scaling. Sorry for putting lot's of queries
No worries. At 7:41 in load balancer configuration, have you chosen internet facing and then put it in the appropriate VPC and subnet where your ec2 instances are running?
@@justmeandopensource haha, I am sure it's difficult but I can also guess that there must be some mini-celeb like feeling too when many people appreciate ya videos
Clear Explaination in the video. I understand how we can create ami when using apache 2 server with index.html file but... If I want to create an ami such with a flask server, such that it starts as soon as I launch the instance. How would I do it? Can you help with this?
Hi Venkat, Could you please help me that how to configure path-based routing in application load balancer for the docker apps through elastic beanstalk deployment.
Hi Yashaswi, thanks for watching this video, I think you get the url endpoint for your elastic beanstalk application you have deployed. This will be the top level url endpoint and the application load balancer is taken care by elastic beanstalk itself. All the routing logic will have to be dealt with the application code you deployed in that environment. For example, when I deploy a Python flask based application, I will get the root url endpoint for my application and other paths will be handled in my flask code. Thanks.
@@justmeandopensource But if I want to configure high availability and want to use an application load balancer and in that there are rules and we can configure path pattern-based routing in that. I am asking about that. like I have deployed docker app to elastic beanstalk by uploading the zip file which has Dockerfile and application jar but now while configuring the elastic beanstalk environment I want application load balancer by default it will take classic but I want to use an application load balancer with path-based routing.
Alright. I understand it now. There is a general documentation on how to configure path-based routing in Application load balancer. docs.aws.amazon.com/elasticloadbalancing/latest/application/tutorial-load-balancer-routing.html And there is Application load balancer configuration documentation related to Elastic Beanstalk which is what you might want to look at. docs.aws.amazon.com/elasticbeanstalk/latest/dg/environments-cfg-alb.html Then under the listeners section, you can configure your paths and health checks. Thanks.
Wonderful explanation, straight to the point. But i'm having one question.. Can we create a elastic load balancer using windows server as an instance ??
@@justmeandopensource yeah thanks , i have tried using windows instance but i cant connect to remote instance. its saying you cannot connect to remote server as it is not available
Hi James, thanks for watching. Error code 502 is internal error which means the actual web service is not running. Please make sure your web application on your ec2 instances are running. Load balancer target group will do health checks to see if the backend ec2 web servers are healthy. Thanks.
@@kayoutube690 I haven't done any videos on that. But its really easy. You can get more details at aws.amazon.com/ec2/instance-types/. Basically they are classified based on the number of CPUs, amount of memory, network speed/throughput and so on.
sir, I have tried at least 10 times but every time ASG checks the health of the instance and deregister it and this I happening again and again. can anyone help me out?
Hi Chetan, thanks for watching. It would be difficult to troubleshoot it remotely. The reason auto scaling group deregisters the target is because it thinks the target is not healthy. You would have defined health check on your target group. And make sure the health check is fine. Example, you might have configured health check on url /health and it should return 200 ok http return code. But if your web application doesn't have /health endpoint, then it is not a proper health check.
@@justmeandopensource yes sir now I am able to do it. Actually my security group won't allow to check the heath of instance that's why in spite of being heathy ASG deregister it. Thanku sir for Concerning my comment.
@@justmeandopensource sir if there is any possibility that i can frequently ask doubt with u. I am preparing for my solution Architect exam. Can u help me sir..
@@chetanyadav5493 I am not concentrating on AWS recently. But if you have questions on any of the videos that I have in this series, I will be happy to help if you ask them in the respective comments section. Cheers.
Hi, thanks for watching. Sure. I will add it to my list. Currently my focus is on the kubernetes series. But will get to this when I get some time. Cheers.
Great Stuff Venkat. Can we have a demo on spot instance provisioning in eks workernodes?it is really helpful as part of aws cost optimisation. Looking forward for the same.
Hi Anil, Thanks for watching this video. I have only recently started this "Learn AWS" series. I have planned lots of videos. I will definitely add this to my list and get it done. Cheers.
Thank you for this video. Question - is there a way to "pin" an instance in the ASG? For example, I always want a t2.micro instance with ID say i-xyz123 and IP address 123.456.78.912 (EIP) to always exist in my AWS account and not get deleted when auto-scaling policy tries to add/remove instances in my account. This instance should have same networking configurations with other instances in ASG i.e. deployed in same region, VPC, IGW, AZ, NACL, subnet, SG and attached to the same ALB/ELB used by those instances in the ASG. Appreciate if you can make a video about this. Thank you in advance.
Hi, thanks for watching. You should be able to prevent a particular instance from being terminated during scale down of ASG. I think its called "Scale In" protection. If you go to the autoscaling page, where it lists your current instances in the ASG group, you can select the instance and click "Set Scale In protection" or something like that. Cheers.
Hi, thank you so much for this video. It was super useful !. One QQ: If I need to scale out or scale in my EC2 instances based on some elb metrics, such as latency or requests count (which are emitted by the elb), how should I do that? E.g. I would be having instances attached to the target group and launched or terminated by ASG, but I want the scaling to be determined by the average latency or the request volume. These 2 metrics are only available for elbs and not for nodes. Is it possible to do this? Thanks.
Hi Teja, thanks for watching. Concepts involved in this video are * Application Load Balancer * Target Group * Launch Configuration * Auto Scaling Group * AMI You will configure an Application Load Balancer which is when you will define the target group. You then create a Launch configuration and then Auto scaling group. In the auto scaling group configuration you specify the load balancer and the target group you created earlier. Now coming to your question, you already have an instance behind the load balancer and need to add Auto scaling group. You already have ALB and target group. What you need now is a launch configuration and auto scaling group. You will have to create an AMI from your current instance and then follow the launch configuration and ASG process. Cheers.
@@tejakirankumarjami9993 As I explained previously, the way ASG works is by having a launch configuration that tells how to launch an instance. You have to create an AMI and launch configuration and let ASG create desired amount of instances. You can't just add instances yourself to an ASG.
Hi venkat, Thank you very much for this tutorial which is very understandable however i want to know if you will do a tutorial on devops like for example deploy kubernetes on aws and CI / CD Thank you
Hi Mouhamed, thanks for watching this video. Yes I have plans to do that as well. I am not sure if you are aware of my other playlist in my channel dedicated for Kubernetes. kubernetes related videos will be uploaded to that playlist. But once I record those videos, I will also add them to this AWS playlist. I am not there yet but will soon record it after doing the ones I have already got in my todo list. Cheers.
@@justmeandopensource Great I just discovered your channel and I take a lot of things with you and and i am verry happy so I'm wating for the new videos thank you
@@mouhamedfall3792 Thanks Mouhamed. I have been uploading videos to "Learn Kubernetes" playlist for over 10 months. Its an ongoing series and you will see 1 video every Monday. Please subscribe for notifications. Cheers.
@@ankireddy5483 Thanks for watching this video. In this video, i installed httpd and created HTML file while launching the instance using the userdata field. Then created an image from that instance. Then created a launch configuration based on that image. Auto scaling group is created with this launch configuration. So basically the html file is baked into the ami. I would suggest following this approach create an instance and configure to your liking and then create an image. Cheers.
I haven't seen the whole video yet and I can't wait to comment "wow" now.
Hi Kay, Many thanks for watching and taking time to comment/appreciate.
Wow
Thanks for watching.
Excellent, no fluff, clear explanation WITH solution diagram so we can visualize the end goal workflow.Thanks for sharing this easy to follow tutorial.
Hi Marc, thanks for watching. Cheers.
Thank you for the simplest explanation
Hi Shaswat, thanks for watching.
So glad I chose your series to begin AWS. No fluff straight to the point, thanks!
Thanks for watching. Cheers.
OMG! I feel more useful and better than UDEMY and CB NUGGETS. Thank you so much brother for your help and the videos. May God bless you!
Hi Jai, thanks for watching this video and you made my day :)
never seen a crystal clear explanation like this!!! . Thank god i found you
Hi Hari, many thanks for watching. Cheers.
I love your channel man. Good explanations of concepts with practical demonstrations and I leave after 20-30 minutes knowing how to do something. Your videos are worth a lot more views than they get.
Hi Ahgee, many thanks for your comment. Much appreciated. Good to know that you are finding this helpful.
I haven't watched the whole video. But topology explanation and steps involved to create an autoscaling group were clearly articulated. That is a big thumb up from me. Believe me, there are a lot of ec2 auto scaling videos out there, but none provides the whole picture from the topology point of view. Well, done.
Hi Guo, many thanks for watching and giving feedback. Cheers.
Awesome explanation, straight to the point
Hi Pradeep, thanks for watching.
Hi Venkat,
Bro HIghly appreciated your efforts, Many peoples get benefited by watching your tutorials. Without excepted anything you’re making efforts really speechless bro.
Once again I would like to say Thanks a lot Bro.
Hi Kumar, Thanks for watching this video and taking time to comment/appreciate. It gives me immense pleasure in sharing my knowledge with others. Cheers.
Everything is clear and explained very well. I'm new to AWS and was able to configure ASG and ELB flawlessly. Thank you for sharing your knowledge.
Hi Leo, thanks for watching. Cheers.
Perfect video with clarity in explaining the concepts. Well done.
Hi Kumar, Thanks for watching.
Wonderful explanation, straight to the point. Many thanks for such an informative stuff!
Cheers
An IT Engineer working in Gemany
Hi Aashish, thanks for watching. Cheers.
want videos on route 53 and more upcoming topics, and you are videos are awesome and very clear. Please keep posting
Hi, thanks for watching. I will definitely be doing more videos in this series. Cheers.
@@justmeandopensource Thanks a lot waiting for more AWS series
@@avs.6avs.613 Will do. Cheers.
I just love the explaination
Thanks for watching.
Man, that was EXCELLENT!!! Thank you.
Hi, thanks for watching. Cheers.
Very Good. complete practical demonstration. Thank you!
Hi, thanks for watching. Cheers.
Simply awesome bro doo more videos.
HI, thanks for watching.
Thanks for this awesome content... really useful.
Hi Asif, thanks for watching.
Good job, I couldn't find a video detailing the whole flow in a such short time.
Hi Pasan, thanks for watching.
Nice & clean video. Keep it up.
Hi Manash, thanks for watching. Cheers.
you saved my life bro. already subscribe on you channel. thank you very much
No worries. Thanks for watching.
Very clear explanation. Straight to the point! Thanks brother
Hi John, thanks for watching. Cheers.
Thanks for this video
Hi Mahmoud, thanks for watching. Cheers.
Glad to see such amazing content on this topic, thank you very much :-)
Hi Shubham, thanks for watching.
THANKS A LOT , VERY WELL EXPLAINED
Hi Shama, thanks for watching. Cheers.
excellent video
Hi Jinen, thanks for watching. Cheers.
You are an amazing teacher. Thank you
Hi Lennon, many thanks for watching.
Hi Venkat, We are waiting for your AWS videos like Route53, S3, ELB, EBS, EC2[ this is very huge topic we want more depth experience on this EC2] and still more VPC practical things like Transit gateway and examples and, You are videos are amazing with clear explanation. Hope you will release your AWS videos asap, and this is the good time to scale up my skills on AWS. Requesting you to kindly do more and more on AWS asap. May God bless you Venkat.
Hi, thanks for your interest in this channel. I will be doing more videos in this series. Currently my focus has shifted to Google Cloud and keeping on top of my Kubernetes series. But will continue this one as well whenever I get some time. Cheers.
Thank you ^^
Thanks for watching.
Thanks so much man !
Hi Dmytro, thanks for watching.
While accessing the dns name of load balncer i am getting 503 service temporary unavailable error
Hi Mayank, thanks for watching. If you get 503, then your web application is not running on the ec2 instances. First test this setup without load balancer and make it work so that you can access the web application. Then introduce the loadbalancer.
@@justmeandopensource Actually it was my fault i attched another target grp to it. Thanks man for such an amazing vdo, i was trying this for whole day yesterdayyy. Stay blessed bro!
@@mayankrawat3942 Ah that explains. Cool.
Sir, I am facing an issue in security groups. When I allowed default route and try to access EC2 instance using SSH it works, but when I use my IP as a source in security group and try to access the instance using ssh, it doesn't work. Please tell me how to figure it out?
Hi, amazing
Thanks for watching.
This configuration is good for static content but what about dynamic changes which is frequently done in daily basis on instance level. WordPress based content are daily changes in /var/www/html/website/folder. how ASG work with that one ?
The same process applies to dynamic websites as well. You have to do all the setup using user data field in launch configuration during bootstrap.
Would I need EFS to connect the information between new instances launched and the original server?
Hi Joseph, thanks for watching.
There is a launch configuration which the Auto scaling group uses to launch similar instances.
Basically everything is baked inside the image itself. So all instances launched by ASG will be identical.
it helped
Hi Akhil, thanks for watching. Cheers.
Hi Venkat.How AWS takes care of stateful applications and auto scale them.?? Web applications are stateless and can be easily scaled.
Hi Anoop, AWS doesn't care whether your applications are stateful or stateless. You have a launch configuration that specifies how to launch the instance and you have auto scaling group that uses this launch configuration. ASG maintains the required number of instances based on scaling policies you define. Thats all AWS does. You will have to make sure how the instances manage the data. You either bake the data within the AMI or use EFS or external NFS for storing data persistently. Cheers.
Hi Venkat,
Very nice topic thank you.
I have implemented route53 with single ec2 instance. I haven't tried with route53 with autoscaling. If you have plan to release this topic in your future video id be happy to wait.
Hi Hareesh, thanks for watching this video. There are lots of topics I have got that are yet to be recorded. I will add this when it comes to Route53 concepts. Thanks for suggesting this topic. Cheers.
I have a question.
What if you need to update the source code of your application?
Can an ELB Classic (CLB) distribute traffic to two different Auto Scaling Groups, both running the same applications? (i.e. Kubernetes Masters in different AZs)
Thanks Buddy. Is it mandatory to have public IP for the EC2 instances?
Is user data is mandate at the time of creating instance or I can install webserver once the instance is created. Have faced a issue while doing the lab error '502' .
Hi Yashwanth, thanks for watching. Userdata field is there just for automation. And it gets executed when the instance is launched. You can always run the commands later after instance started if you don't want to use user data.
@@justmeandopensource Thank you for answering my query. I am facing error 502 , showing instance health status as unhealthy and new instance are coming up . But this was going into loop. No actual output observed . Completely lost my weekend to achieve still no luck.
@@yashwanth4786 I think the health check is failing. The load balancer will route traffic only to the ec2 instances that are healthy. For some reason they don't seem to be healthy. So your web application might not be running properly. Just launch a separate ec2 instance from the ami and see if the web server is running.
@@justmeandopensource i have tried to access nginx default page on general instance. Am not able to access same O/P when the instances were under auto scaling.
Sorry for putting lot's of queries
No worries. At 7:41 in load balancer configuration, have you chosen internet facing and then put it in the appropriate VPC and subnet where your ec2 instances are running?
helpful!
Thanks for watching.
@@justmeandopensource there are many comments in this section and you have replied to each one of them. That's wonderful.
@@nitiz281 I try my best to respond to everyone but thats is getting increasingly difficult to keep up these days 😀
@@justmeandopensource haha, I am sure it's difficult but I can also guess that there must be some mini-celeb like feeling too when many people appreciate ya videos
@@nitiz281 yeah definitely. Thats the motivation behind me keeping up with new videos.
Clear Explaination in the video. I understand how we can create ami when using apache 2 server with index.html file but...
If I want to create an ami such with a flask server, such that it starts as soon as I launch the instance. How would I do it?
Can you help with this?
Sir, how to configure ELB with auto scaling for database and file upload server, please help me...
Hi Venkat,
Could you please help me that how to configure path-based routing in application load balancer for the docker apps through elastic beanstalk deployment.
Hi Yashaswi, thanks for watching this video, I think you get the url endpoint for your elastic beanstalk application you have deployed. This will be the top level url endpoint and the application load balancer is taken care by elastic beanstalk itself. All the routing logic will have to be dealt with the application code you deployed in that environment.
For example, when I deploy a Python flask based application, I will get the root url endpoint for my application and other paths will be handled in my flask code.
Thanks.
@@justmeandopensource But if I want to configure high availability and want to use an application load balancer and in that there are rules and we can configure path pattern-based routing in that. I am asking about that. like I have deployed docker app to elastic beanstalk by uploading the zip file which has Dockerfile and application jar but now while configuring the elastic beanstalk environment I want application load balancer by default it will take classic but I want to use an application load balancer with path-based routing.
Alright. I understand it now.
There is a general documentation on how to configure path-based routing in Application load balancer.
docs.aws.amazon.com/elasticloadbalancing/latest/application/tutorial-load-balancer-routing.html
And there is Application load balancer configuration documentation related to Elastic Beanstalk which is what you might want to look at.
docs.aws.amazon.com/elasticbeanstalk/latest/dg/environments-cfg-alb.html
Then under the listeners section, you can configure your paths and health checks.
Thanks.
@@justmeandopensource thanks Venkat... If possible please prepare video on same.elatsic beanstalk with application load balancing... :)
@@yashaswisharma841 Sure.
HI VENKAT, Great videos , Please let us know about Placement groups and cloud formation
Wonderful explanation, straight to the point.
But i'm having one question..
Can we create a elastic load balancer using windows server as an instance ??
Hi Akash, thanks for watching. You can use load balancer with any backend instances.
@@justmeandopensource yeah thanks , i have tried using windows instance but i cant connect to remote instance.
its saying you cannot connect to remote server as it is not available
@@AKASHRAJ79 In theory, you should be able to and as I don't have the full context of what you are doing, my assistance will be very limited.
@@justmeandopensource tq sir for help
@@AKASHRAJ79 you are welcome.
Hello, Do you know how to fix this issue shows on my Load Balancer under Target Group. "Health checks failed with these codes: [502]"
Hi James, thanks for watching. Error code 502 is internal error which means the actual web service is not running. Please make sure your web application on your ec2 instances are running. Load balancer target group will do health checks to see if the backend ec2 web servers are healthy. Thanks.
@@justmeandopensource thank you.
@@kayoutube690 You are welcome. Cheers.
@@justmeandopensource sir do you have tutorial for the different instance type in aws?
@@kayoutube690 I haven't done any videos on that. But its really easy. You can get more details at aws.amazon.com/ec2/instance-types/. Basically they are classified based on the number of CPUs, amount of memory, network speed/throughput and so on.
Textbook of the AWS
Hi First Last, thanks for watching this video and taking time to comment. Cheers.
sir, I have tried at least 10 times but every time ASG checks the health of the instance and deregister it and this I happening again and again.
can anyone help me out?
Hi Chetan, thanks for watching. It would be difficult to troubleshoot it remotely. The reason auto scaling group deregisters the target is because it thinks the target is not healthy. You would have defined health check on your target group. And make sure the health check is fine. Example, you might have configured health check on url /health and it should return 200 ok http return code. But if your web application doesn't have /health endpoint, then it is not a proper health check.
@@justmeandopensource yes sir now I am able to do it. Actually my security group won't allow to check the heath of instance that's why in spite of being heathy ASG deregister it.
Thanku sir for Concerning my comment.
@@justmeandopensource sir if there is any possibility that i can frequently ask doubt with u. I am preparing for my solution Architect exam. Can u help me sir..
@@chetanyadav5493 Perfect.
@@chetanyadav5493 I am not concentrating on AWS recently. But if you have questions on any of the videos that I have in this series, I will be happy to help if you ask them in the respective comments section. Cheers.
Great video! Wondering if you can do an update video since the consoles have all been refreshed with a new user experience.
Hi, thanks for watching. Sure. I will add it to my list. Currently my focus is on the kubernetes series. But will get to this when I get some time. Cheers.
Great Stuff Venkat. Can we have a demo on spot instance provisioning in eks workernodes?it is really helpful as part of aws cost optimisation. Looking forward for the same.
Hi Anil, Thanks for watching this video. I have only recently started this "Learn AWS" series. I have planned lots of videos. I will definitely add this to my list and get it done. Cheers.
why you created the AMI and deleted it in the last
Hi Duraivel, thanks for watching. I deleted the AMI at the end as part of cleaning up.
Thank you for this video. Question - is there a way to "pin" an instance in the ASG? For example, I always want a t2.micro instance with ID say i-xyz123 and IP address 123.456.78.912 (EIP) to always exist in my AWS account and not get deleted when auto-scaling policy tries to add/remove instances in my account. This instance should have same networking configurations with other instances in ASG i.e. deployed in same region, VPC, IGW, AZ, NACL, subnet, SG and attached to the same ALB/ELB used by those instances in the ASG. Appreciate if you can make a video about this. Thank you in advance.
Hi, thanks for watching. You should be able to prevent a particular instance from being terminated during scale down of ASG. I think its called "Scale In" protection. If you go to the autoscaling page, where it lists your current instances in the ASG group, you can select the instance and click "Set Scale In protection" or something like that. Cheers.
@@justmeandopensource noted. Thanks!
@@zulhilmizainudin You are welcome. Cheers.
Hi, thank you so much for this video. It was super useful !. One QQ: If I need to scale out or scale in my EC2 instances based on some elb metrics, such as latency or requests count (which are emitted by the elb), how should I do that? E.g. I would be having instances attached to the target group and launched or terminated by ASG, but I want the scaling to be determined by the average latency or the request volume. These 2 metrics are only available for elbs and not for nodes. Is it possible to do this? Thanks.
Hi Mahesh, thanks for watching. See if this helps docs.aws.amazon.com/autoscaling/ec2/userguide/as-scaling-target-tracking.html
Hi Venkat, Thanks for the amazing video, how do i connect elastic IP to load balancer?
Hi, thanks for watching. I need more details of what you are trying to do so that I can offer advice. Cheers .
Thankyou so much for you video...
If I have my instanced already added to my ELB and now I want those to be added to ASG.. is it possible
Hi Teja, thanks for watching.
Concepts involved in this video are
* Application Load Balancer
* Target Group
* Launch Configuration
* Auto Scaling Group
* AMI
You will configure an Application Load Balancer which is when you will define the target group. You then create a Launch configuration and then Auto scaling group. In the auto scaling group configuration you specify the load balancer and the target group you created earlier.
Now coming to your question, you already have an instance behind the load balancer and need to add Auto scaling group. You already have ALB and target group. What you need now is a launch configuration and auto scaling group. You will have to create an AMI from your current instance and then follow the launch configuration and ASG process.
Cheers.
Just me and Opensource hi there, thank you for your reply, so what I understand is we cannot add the existing ones under ASG right
@@tejakirankumarjami9993 As I explained previously, the way ASG works is by having a launch configuration that tells how to launch an instance. You have to create an AMI and launch configuration and let ASG create desired amount of instances. You can't just add instances yourself to an ASG.
Hi venkat,
Thank you very much for this tutorial which is very understandable
however i want to know if you will do a tutorial on devops like for example deploy kubernetes on aws and CI / CD
Thank you
Hi Mouhamed, thanks for watching this video. Yes I have plans to do that as well. I am not sure if you are aware of my other playlist in my channel dedicated for Kubernetes. kubernetes related videos will be uploaded to that playlist. But once I record those videos, I will also add them to this AWS playlist. I am not there yet but will soon record it after doing the ones I have already got in my todo list. Cheers.
@@justmeandopensource
Great
I just discovered your channel and I take a lot of things with you and and i am verry happy so I'm wating for the new videos
thank you
@@mouhamedfall3792 Thanks Mouhamed. I have been uploading videos to "Learn Kubernetes" playlist for over 10 months. Its an ongoing series and you will see 1 video every Monday. Please subscribe for notifications. Cheers.
What is "hotch" ttpd?
Hi Andrew, thanks for watching this video. I have no idea what you are talking about.
if i want to change code in server ,how can i send code ,if change code in one server what about another server
i want to change code hello world to hello people then wre i have to change bro ,please reply me
@@ankireddy5483 Thanks for watching this video. In this video, i installed httpd and created HTML file while launching the instance using the userdata field. Then created an image from that instance. Then created a launch configuration based on that image. Auto scaling group is created with this launch configuration. So basically the html file is baked into the ami.
I would suggest following this approach create an instance and configure to your liking and then create an image. Cheers.
@@justmeandopensource configure to your liking means ?
@@ankireddy5483 Configure the web server like how you want it.
@@justmeandopensource okay thanks for replying bro ,will try ....
So well explained. Thanks a lot.
Hi Mario, thanks for watching. Cheers.