![]() ![]() The AMI from A was deployed on B and it worked as well. The AMI from B was deployed on A and it worked. So just to be clear.īoth AMI from the 2 machines worked on the subnets. I've created an AMI of the working instance that's on 10.0.0.0 and deployed it on 10.0.1.0, and it worked. Is this something related to public IP's? Account limitation? Surprising that worked, now I have 3 machines, 2 of them on the same subnet sending metrics over 5001, and the other one returning timeout. I've decided to create an AMI of the instance on 10.0.0.0 and deploy a new machine on the same subnet and AZ. The instance that's working is also on the same AZ of the monitoring machine (us-east-1a), the one that doesn't work is on (us-east-1b).Īfter a lot of tcpdump and troubleshooting, cause other ports works like, 80, 443, 4001. For some reason the tcp communication on port 5001 doesn't work on the machine that's using the subnet 10.0.1.0, but it works on the using the subnet 10.0.0.0. Both on same VPC, same security group, same route table and ACL. We setup a monitoring instance scraping an exposed endpoint on 2 different instances. I'm a little curious and confused about this situation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |