Questions tagged with Classic Load Balancer
Content language: English
Sort by most recent
Over the past week, clients have reported that any downloads approximately 600+ MB will be terminated mid request within a few seconds of the original request starting. I've checked multiple places to make sure its not my app that's dropping the connection or the EC2 instance and have verified that instances outside the Classic ELB can download the same file just fine.
My production workload is in Opsworks Stacks and I bring up and take down the webservers according to load, and time of day. Opsworks very cleanly adds the instances to the load balancer after they come up and removes the instance from the load balancer before shutting down. I have looked into migrating to NLB or ALB, however since AWS still does not support those load balancers in Opsworks Stacks I am stuck using the Classic Load Balancer.
After pounding my head against the wall I opened a support ticket to report a possible problem. AWS Support confirms the bug is known and "Classic Load Balancer experiences high resource utilization, when large files are being uploaded and downloaded to or from the target EC2 instances". Also I was informed there is no ETA of a fix. This was April 11, I have escalated to my account manager as well, but apparently he has not been able to get any traction either.
I am posting so there is visibility.
My POST requests to my Elastic Beanstalk instance take a lot longer (over a minute) than my GET requests even though I have them doing the same thing. I created an experiment where the POST request and GET request both read the same thing from my RDS service (which is in a private subnet) and the POST requests take significantly longer. Does anyone know what might be the issue here?
I deployed a .NET Core 3.1 app to an Elastic Beanstalk 64bit Windows Server Core 2019 v2.9.0 instance running IIS 10.0 on my public subnet which reads data from an RDS Postgres instance on a private subnet within a custom VPC. In order to send HTTPS requests, I have this instance behind the classic load balancer and my custom domain name has a CNAME record pointing to the load balancer DNS record.
Hi team,
i bought domain amazon jeevanresume.link but when i trying to access its not working even i mapped ELB to rout53 domain by creating records is anything i should do after buying domain
other than email confirmation
Quite sure this has been answered in previous forums, Do ELB IP (classic/alb not NLB) change over time?
If it does change, does it change for all AZs that I have enabled load balancer to?