amazon-elb

If i use Cloudfront to sit in front of a webserver, which itself is behind an ELB, would the following apply? I use Route53 to create a domain name record for the CF domain and apply an SSL certificate to that domain to secure the distribution If CF can not serve the content from the cache then the SSL connection is forward to the the ELB (which fronts the webserver as an origin server) Therefore i also need to use the same domain name (FQDN) on the ELB (via Route53 CNAME) and apply the same cert there too? When CF forwards the request through the ELB the SSL is terminated Is that right ? Will

I'm running servers in a AWS auto scale group. The running servers are behind a load balancer. I'm using the ELB to mange the auto scaling groups healthchecks. When servers are been started and join the auto scale group they are currently immediately join to the load balancer. How much time (i.e. the healthcheck grace period) do I need to wait until I let them join to the load balancer? Should it be only after the servers are in a state of running? Should it be only after the servers passed the system and the instance status checks? There are two types of Health Check available for Auto

I have an EC2 instance with Apache as a reverse proxy and ffserver as a streaming server. There is an ELB (Classic) in front of the EC2 instance which works as an SSL termination point. Apache configuration is rather simple: <Location "/mp3/"> ProxyPass http://127.0.0.1:8081/ DisableReuse=On KeepAlive=Off ProxyPassReverse http://127.0.0.1:8081/ SetEnv force-proxy-request-1.0.1 SetEnv proxy-nokeepalive 1 </Location> ffserver is used to stream live audio over the Internet. In ffserver 's settings there is a MaxBandwidth option (default 1000 ). This setting become a problem when the connections

When having a bunch of systems that act as WebSocket drones and a Load Balancer in front of those drones. When a WebSocket request comes into the LB it chooses a WebSocket drone, and the WebSocket is established. (I use AWS ELB tcp SSL-terminated at ELB) Question: Now does the created WebSocket go through the LB, or does the LB forward the WebSocket request to a WebSocket drone and thus there is a direct link between client and a WebSocket drone? If the WebSocket connection goes through the LB, this would make the LB a huge bottleneck. Removing the LB and handing clients a direct IP of a

I've a REST API application running in two EC2 instance and was using AWS Classic Load Balancer for a long time. The clients of REST API rely on the response headers (e.g. such as Location ). I know that HTTP headers are case-insensitive by definition, however (unfortunately) some clients are ignoring this and checking the headers in a case-sensitive way (e.g. they expect Location to start with upper case). Recently I've changed to AWS Application Load Balancer and now I see that it transforms all response headers to lower case, as a result clients are failing to handle the response properly.

Closed. This question is off-topic. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it's on-topic for Stack Overflow. I am looking for a way to drop connections from known spam ip addresses on an Amazon's Elastic Load Balancer (ELB)? I am currently doing this at the web server level (multiple instances, running behind the ELB), but wondering if there is a way to do it at the ELB. This way, I can avoid configuring each web server instance for this. I typically pull the Drop List from Spamhause.org every day and update my web server