amazon-elb

问题 I am currently switching over an application to amazon but I'm noticing that sometimes the response I receive is a 504. Our system is setup in a way where we have a LB in front of our ELB and then it goes straight to tomcat. We are currently timing all our requests in our service and in the servlet filter logging the response time and they are always less than 1s. We then look at the LB logs and are seeing a 504 and it appears that somehow the ELB is timing out and returning the 504. Does

问题 Here is my config file <VirtualHost *:80> ServerAdmin webmaster@localhost DocumentRoot /var/www/html Redirect permanent / https://www.mywebsite.co/ ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined </VirtualHost> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet And when I type in the browser mywebsite.co it successfully redirects me https://mywebsite.co however content does NOT render on the page because of this error (by Google Chrome) Error 310 (net::ERR_TOO

问题 We're using Amazon Web Services (AWS) and we have multiple web servers and a load balancer. The problem with the web servers is, that the $_SESSION is unique for each one. I'm keeping some information about the user in the $_SESSION. What is the proper way to synchronize this information? Is there any way to unite the place, where those sessions are being kept, or should I use MySQL to store this data (I don't really like the last option)? 回答1: I think what you are looking for is 'Sticky

问题 I'm pretty stuck with this thing for couple of hours. No way I could make it working. I tried everything I can think of and/or found online. So, my application is pointed to ELB (web). ELB listens to 80 and 443 and sends traffic to 80 (SSL is terminated here) to member instance(s) which is nginx. Nginx proxies app requests to another ELB (app) in front of multiple instances. These instances run puma. Everything works fine except when I try visiting an URL (where I used force_ssl for that

问题 I am pretty much new to AWS. I was trying to list the load balances which are not attached to any of the instances. I was trying describe-load-balancers using aws cli but was not able to get an option that filters the elbs. Please provide some suggestions on how to achieve this. 回答1: Assuming you have aws cli setup with suitable keys, this long line of shell should list the ELBs with a count of instances attached to them. If it says zero then there are no instances attached for i in `aws elb

问题 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

问题 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

问题 I installed CentOS Atomic Host as operating system for kubernetes on AWS. Everything works fine, but it seems I missed something. I did not configure cloud provider and can not find any documentation on that. In this question I want to know: 1. What features cloud provider gives to kubernetes? 2. How to configure AWS cloud provider? UPD 1 : external load balancer does not work; I have not tested awsElasticBlockStore yet, but I also suspect it does not work. UPD 2 : Service details: $ kubectl

问题 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,

问题 How do you put up a maintenance page in AWS when you want to deploy new versions of your application behind an ELB? We want to have the ELB route traffic to the maintenance instance while the new auto-scaled instances are coming up, and only "flip over" to the new instances once they're fully up. We use auto-scaling to bring existing instances down and new instances, which have the new code, up. The scenario we're trying to avoid is having the ELB serve both traffic to new EC2 instances while