amazon-elb

I am working on a POC to prove out AWS path based routing through an Application Load Balancer to a set of very basic "hello world" node.js applications using express. Without the path based routing in place and having multiple listeners, 1 listener for each application, each respective listener and application is working as expected. Therefore, the targets within the Target Groups have both passed health checks and are shown as healthy. However, when I switch to the path based routing implementation on 1 of the listeners (deleting the other unnecessary listener) I get the following error for

I am using Amazon Web Services EC2 Container Service with an Application Load Balancer for my app. When I deploy a new version, I get 503 Service Temporarily Unavailable for about 2 minutes. It is a bit more than the startup time of my application. This means that I cannot do a zero-downtime deployment now. Is there a setting to not use the new tasks while they are starting up? Or what am I missing here? UPDATE: The health check numbers for the target group of the ALB are the following: Healthy threshold: 5 Unhealthy threshold: 2 Timeout: 5 seconds Interval: 30 seconds Success codes: 200 OK

Is it possible to load balance MQTT broker? Can I use ELB to load balance MQTT? Any pointers in this direction would be helpful. I hit upon http://www.slideshare.net/kellogh/mqtt-kafka-33100776 but it did not help much. Use HAProxy . A free, fast and reliable solution offering high availability, load balancing and proxying for TCP and HTTP based applications. It’s suited for very high traffic web sites. Load balancing MQTT brokers is not supported out-of-the-box by most MQTT brokers. There are brokers available which support clustering, though. Take a look at this list to find out a broker

I'm trying to get my websockets working with Amazon Web Service and Elastic Beanstalk (ELB). I set up a proxy protocol according to: http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/enable-proxy-protocol.html I've opened up all inbound traffic to my load balancer and other security groups on all ports, for all IPs. I also kept the load balancer listerner as HTTP on port 80. My websocket connection gives the following error when trying to connect on port 80: failed: Error during WebSocket handshake: Unexpected response code: 400 And this error on port 8080: failed: Error in

I am trying to set up Elastic Load Balancing (ELB) in AWS to split the requests between multiple instances. I have created several images of my webserver based on the same AMI, and I am able to ssh into each individually and access the site via each distinct public DNS. I have added each of my instances to the load balancer, but they all come back with the Status: Out of Service because they failed the health check. I'm mostly confused because I can access each instance from its public DNS, but I get a timeout whenever I visit the load balancer DNS name. I've been trying to read through all

Is it possible to force nginx $scheme value to "https" if nxinx is running behind load balancer? In my scenario Load balancer takes care of https communication with client and forwards requests to nginx as raw http. I know I can do something like this to detect https set $my_scheme "http"; if ($http_x_forwarded_proto = "https") { set $my_scheme "https"; } but I'm just curious if there is something like real_ip_header function for IPs. Are there also some headers I need to update when detecting https manualy? Our setup is the same as yours, only using map instead of if/set (as recommended by