@@BeCloudGuru I have a HADR setup for two IBM database. One will be primary and other will secondary. Both the database will be up and running all the time but the request that goes to secondary database will fail . For this reason, i wasnt able to use the network load balancer. The only option i came across so far is to use the R53 failover . All our server's are private IP's and so i cant be able to use endpoint url to check the status of the database server on port . Not sure on other monitor's like state of CloudWatch alaram and calculated health check
That's good explanation, whenever primary resource fails, its switches to secondary resource as you explained, but how can we switch back to the primary resource when it regained its health
@Kiran, thanks for watching the video and providing your feedback, when your primary resource comes back health check would find that and after passing the healthy threshold it ll be back in the service,if yours is not coming back then check the ip address whether it's the same or not after the instance come back.
@@BeCloudGuru Thanks for the quick response. You created only one health check right? So it continuously checks for the primary resource health and when it fails it switches to secondary. From your above response, I understand that the health check which you created keeps on checking whether the primary resource regained its health, if it comes back into activate state, it again switches back to primary. This is my understanding correct me if I am wrong
@@kiranrao7429 yes your understanding is correct but as I created only one health check it only checks the primary one doesn't switch to secondary, once primary comes back and health check find it healthy it would start the process to bring it in the service,but having said that I feel you are using the public ip which tends to change when you stop and start an instance, I'm that case as we have our health check looking for the previous IP it won't be able to determine whether our primary instance has come back or not so use an Elastic IP or modify the IP of health check to see the primary instance coming back in action once you simulate that recovery of it, I hope it make things clear
Hi cloudguru..... Can you provide project based questions for L1 level. In AWS solutions architect. So that I can get a good job. If these are paid please provide I will pay for it.
@@BeCloudGuru sir e.g. take an example of aws migration. An interviewer asked what kind of issues you feced in AWS migration ( from vm to aws, or from physical server to aws, or from storage to aws ). That kind of sir.. or any questions which will benefit me to get a job in aws
Excellent demonstration
Nice video. What if my EC2 instance is a private ip address and also i need to do health check using tcp on a port?
@Avinash, thanks for watching, can you elaborate your scenario please.
@@BeCloudGuru I have a HADR setup for two IBM database. One will be primary and other will secondary. Both the database will be up and running all the time but the request that goes to secondary database will fail . For this reason, i wasnt able to use the network load balancer. The only option i came across so far is to use the R53 failover . All our server's are private IP's and so i cant be able to use endpoint url to check the status of the database server on port . Not sure on other monitor's like state of CloudWatch alaram and calculated health check
That's good explanation, whenever primary resource fails, its switches to secondary resource as you explained, but how can we switch back to the primary resource when it regained its health
@Kiran, thanks for watching the video and providing your feedback, when your primary resource comes back health check would find that and after passing the healthy threshold it ll be back in the service,if yours is not coming back then check the ip address whether it's the same or not after the instance come back.
@Kiran Also please consider subscribing if you liked the content.
@@BeCloudGuru Thanks for the quick response. You created only one health check right? So it continuously checks for the primary resource health and when it fails it switches to secondary. From your above response, I understand that the health check which you created keeps on checking whether the primary resource regained its health, if it comes back into activate state, it again switches back to primary. This is my understanding correct me if I am wrong
@@kiranrao7429 yes your understanding is correct but as I created only one health check it only checks the primary one doesn't switch to secondary, once primary comes back and health check find it healthy it would start the process to bring it in the service,but having said that I feel you are using the public ip which tends to change when you stop and start an instance, I'm that case as we have our health check looking for the previous IP it won't be able to determine whether our primary instance has come back or not so use an Elastic IP or modify the IP of health check to see the primary instance coming back in action once you simulate that recovery of it, I hope it make things clear
Thank you so much
Nice
Hi cloudguru..... Can you provide project based questions for L1 level. In AWS solutions architect. So that I can get a good job. If these are paid please provide I will pay for it.
@karamjeet, What kind of questions you are looking for, great job should be based on your knowledge not on a set of questions my friend
@@BeCloudGuru sir e.g. take an example of aws migration. An interviewer asked what kind of issues you feced in AWS migration ( from vm to aws, or from physical server to aws, or from storage to aws ). That kind of sir.. or any questions which will benefit me to get a job in aws
@Karamjeet, all these questions are experience based, let's discuss it @sginfotech16@gmail.com
@@BeCloudGuru ok sir