amazon web services - Testing classic internal ELB -
i have configured , passed health check aws elb(load balancer), trying ping or send packet tcp port 9300 there no ip address elb. have ec2 instance @ end of elb has elasticsearch running on it.
the elb configured internal elb doesn't have public ip address it. wondering if there way can ssh? or ping elb? pretty new aws , read trouble shooting aws official website, couldn't find solution.
the goal trying achieve test whether internal amazon ec2 load balancer working properly. got internal elb ip address ping command, however, not able ping or crul ip address. know doing wrong. way want access private network in correct?
an elastic load balancer presented single service, consists of several load balancing servers spread across subnets , availability zones nominate.
when connecting elastic load balancer, should always use dns name of elastic load balancer. resolve 1 of several servers providing load balancing service.
load balancers designed pass requests , return responses. next time user sends request, might sent different back-end service. thus, web-type traffic not suitable situations requiring permanent connection, such ssh. can configure sticky sessions http connections use cookies send user same back-end server if required.
the classic elastic load balancer supports tcp protocol, these requests distributed in round-robin fashion back-end servers not suitable long-lasting sessions.
bottom line: great request/response traffic needs distributed across multiple back-end servers. not suitable ssh.
site-note: using ping test services isn't idea. ping turned off in security groups default since can expose services , isn't security perspective. should test connectivity connecting via expected protocols (eg http requests) rather using ping. applies testing ec2 connectivity, too.
Comments
Post a Comment