I created a ELB facing on the Internet, and it creates a VPC (10.1.0.0/16), two subnets (both under the cn - north - 1 a, segment respectively 10.1.0.0/24 (subnet1) and 10.1.1.0/24 (subnet2)), in subnet1 creates two instances for dealing with traffic, instances are installed HTTPD and test page can be acquired through the curl information, because is to test the security group and ACL is completely open,

My understanding of the ELB is a usable area such as public of cn - north - 1 a subnet configures instances are added to the available after ELB area can be added to the ELB, as long as the security group set up correctly, and ELB processing request to forward the request to the instance after instance ELB will no longer control the request, this time instance will directly communicate with the request of the client, so instance is also need to be able to access the Internet, because China has not yet been NAT service, so I joined the point to the Internet gateway in subnet1 route, the previously created two instances are created automatically assigned the public IP (don't know whether understand so),

Situation now is: adding public subnet subnet2 ELB, create two instances with public IP in subnet1 and add instance to the ELB, for instance can connect Internet so in subnet1 have also joined the route to IGW, open all the security group,

Finally enter ELB DNS in the browser, can get the page instance, every time is not creating ELB can get to the instance, and every time, even if access to the instance, after a period of time also can't get, and I'll subnet1 is two instances in the subnet to join ELB cannot obtain, but ELB DNS is always able to ping, remain the InService instances, excuse me this kind of phenomenon is why?

CodePudding user response:

Didn't met this

CodePudding user response:

reference 1st floor xiongshengwu response:

didn't met this kind of

Hello, excuse me the above configuration process is there a problem? Is a in the cn - north - 1 a has two subnets, are the route to IGW (because I understand it is an instance in ELB to and Internet communications but NAT can't use, can I do?), one of the added to the ELB, another subnet creates two instances and add to the ELB,
Security groups are no problem for ping ELB, also InService instance,