amazon-elb

问题 Is there any way to support multiple health endpoints on a Spring Boot application? Here's why: The standard actuator health check is great, built in checks are great, customization options are great - for a single use case: reporting on general application health. But I'd like something I can call from an AWS Elastic Load Balancer / AutoScaling Group. By default, if an instance fails a health check, the ELB/ASG will terminate it and replace it with a fresh instance. The problem is some of

问题 Is there any way to support multiple health endpoints on a Spring Boot application? Here's why: The standard actuator health check is great, built in checks are great, customization options are great - for a single use case: reporting on general application health. But I'd like something I can call from an AWS Elastic Load Balancer / AutoScaling Group. By default, if an instance fails a health check, the ELB/ASG will terminate it and replace it with a fresh instance. The problem is some of

问题 We're running a web API app on Kubernetes (1.9.3) in AWS (set with KOPS). The app is a Deployment and represented by a Service (type: LoadBalancer) which is actually an ELB (v1) on AWS. This generally works - except that some packets (fragments of HTTP requests) are "delayed" somewhere between the client <-> app container. (In both HTTP and HTTPS which terminates on ELB). From the node side : ( Note: Almost all packets on server-side arrive duplicated 3 times ) We use keep-alive so the tcp

问题 AWS's new Application Load Balancer is throwing an error : 400 Bad Request, Request Header Or Cookie Too Large, awselb/2.0 How do i increase the size in aws-elb. It was working fine with the classic load balancer. 回答1: we spoken to aws about the same issue, we were sending a header request of a total of 33k, but one of our header ( authorization) size was 30 , but the limit ALB accepts for is as follows : - 16K per request line - 16K per single header - 64K for the entire header 回答2: This 400

问题 I have created an SSL cert via DigiCert and imported to ACM. (I require the same SSL to be applied to both ALB and the Application, and since there's no way to import ACM certs, I had to follow this way) I have successfully imported the SSL and can see it in the console. However, I cannot apply it to ALB 443 Listener. I provided the Cert ARN to the CloudFormation template and it fails stating certificate don't exist. I have tried to manually update the 443 Listener, but the cert is not listed

问题 I'm having trouble. I followed a guide that I found here http://www.thenetworkadministrator.net/index.php/2011/12/iis-ssl-certificate-into-amazon-elastic-load-balancer/ And exported by cert and created all those files, but it doesn't tell you which file goes in which field. I tried what I think is all the combinations but it doesn't accept it I Setup the balancer as follows Then I try to setup the certificate Then you can see it tells me it's invalid. In case it helps I exported from IIS and

问题 I'm having trouble. I followed a guide that I found here http://www.thenetworkadministrator.net/index.php/2011/12/iis-ssl-certificate-into-amazon-elastic-load-balancer/ And exported by cert and created all those files, but it doesn't tell you which file goes in which field. I tried what I think is all the combinations but it doesn't accept it I Setup the balancer as follows Then I try to setup the certificate Then you can see it tells me it's invalid. In case it helps I exported from IIS and

问题 I'm having trouble. I followed a guide that I found here http://www.thenetworkadministrator.net/index.php/2011/12/iis-ssl-certificate-into-amazon-elastic-load-balancer/ And exported by cert and created all those files, but it doesn't tell you which file goes in which field. I tried what I think is all the combinations but it doesn't accept it I Setup the balancer as follows Then I try to setup the certificate Then you can see it tells me it's invalid. In case it helps I exported from IIS and

问题 Load balancers cost an hourly rate (Re)creating EB costs uploads to S3 and takes a long time So for EB that is sitting idle (used only during development), just as EC2 can be scaled down to 0 instances, how can the load balancer be toggled off (and later toggled back on)? Could Terraform be employed, such that the absence of the ALB is detected and gets recreated with an apply? I already terminate EC2 instances under EB when idle, but all the while my unused load balancer is charging me!

问题 Load balancers cost an hourly rate (Re)creating EB costs uploads to S3 and takes a long time So for EB that is sitting idle (used only during development), just as EC2 can be scaled down to 0 instances, how can the load balancer be toggled off (and later toggled back on)? Could Terraform be employed, such that the absence of the ALB is detected and gets recreated with an apply? I already terminate EC2 instances under EB when idle, but all the while my unused load balancer is charging me!