Questions tagged with Classic Load Balancer
Content language: English
Sort by most recent
Hi,
I am trying to get the service quota for Classic Load Balancers using the SDK for Go. When I attempt to retrieve it using the service code `elasticloadbalancing` and the quota code `L-E9E9831D`, I get a proper and normal response with every value filled out *except* the actual quota `value`. This is nil, and I have no idea why. If I use the CLI to get the service quota for these exact same service and quota codes, I get the quota value on the account. But in the SDK, I get a nil value.
Any ideas? Is this a bug?
Hello,
Using this link as a guide https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/configuring-https.html
I added an AWS "classic" load balancer to an existing elastic beanstalk environment (accepted default load balance settings); the listener was updated to include https on port 443 with an AWS provided SSL certificate.
After applying these settings, the website is only available as http://bsatroop706.org/index (the https url is does not accept a browser request). What additional configuration might be needed to enable SSL/TLS? The https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/configuring-https.html doesnt indicate if additional configuration is needed...
Ideas appreciated
I realise that LightSail is an entry level provision that enables people like me who sadly don't know near enough to tap into what is pretty amazing tech. However, it's very frustrating that things that should work just as a result of a few clicks definitely DO NOT. Furthermore, most of the documentation is outdated or lack sufficient detail. Does AWS really want to charge $18 per month for something this buggy / filling up countless forums with people expressing their difficulties and frustrations??
For over a day now (8+ hours) I have tried in vain to set up a Load balancer connected to two Wordpress / Bitnami Instances. First the DNS related to the LB *7668[...].eu-west-2.elb.amazonaws.com* was clearly broken in that clicking that link returned a Safari couldn't open the page error:
> **Safari can’t open the page “7668[...].eu-west-2.elb.amazonaws.com” because Safari can’t find the server “7668[...].eu-west-2.elb.amazonaws.com”.**
Having found out the relevant IP I was able to load the page, but still...
But it is when it comes to setting things up within the DNS zone where the trouble really begins. When assigning my domain to a Static IP address associated with one of my instances everything works fine—but obviously the load balancer is not "active"; i.e. traffic to my domain goes straight to the instance. However when assigning the domain to the LoadBalancer (with certificates, validated, etc.) the page instantly "breaks" with the error message:
> **"Too many redirects occurred trying to open “https://7668[...].eu-west-2.elb.amazonaws.com”. This might occur if you open a page that is redirected to open another page, which then is redirected to open the original page."**
At this point there's zero help from within Lightsail and none of the docs (mostly outdated or overly vague) cover this. So I hit various forums, searching and the problem seems to be all over the place with countless solutions, none of which however work... I can't help thinking this problem would be very simple for someone knowledgeable to fix, but there's certainly no way within Lightsail to solve this... MEGA FRUSTRATING.
As such, after 8+ hours, I now deleted the Load balancer (not wanting to be charged for something that doesn't work) and returned to serving my website content from a single instance.
What am I missing? Why is such a no doubt simple problem for those in the know, seemingly insurmountable for the kind of audience Lightsail is aimed at? What is the solution?
Thank you :)
I moved my domain that I bought route 53 to another aws account through Terminal-CMD, it worked perfectly, I created the zones hosted on router 53, but when I create the type A record so that my ec2 instance appears when they search for my domain on the internet it does not appear Nothing, it just gives me an error and adding the load balancer doesn't work either, it doesn't work with a static IP, balancer or latency. I don't know what to do anymore, I need help. I am very new to aws.
I have an elasticbeans environment that had been using an "classic" load balancer. I ran the widget to update that to an Application load balancer. But EBS is still pointing at the classic instance, which is gone. Its not obvious how to fix this without rebuilding. I can change the config of the ELB, but not extract it and replace with with other - at least not through the GUI. I saw an answer from 2 years ago that suggested a rebuild was the only option - but I'm hoping there has been an update. Any suggestions?
i have 1 instances , so can i use application load balancer ?
When trying to create a new Route 53 record and enabling **Alias**, all options under "**Route traffic to**" except for "another record in this hosted zone" are greyed out and unavailable to select. I am trying to point a CNAME to my active ELB, but cannot select "**Alias to Application and Classic Load Balancer**"
Any reason all the options would be disabled? Account permissions? Security settings?
Hello,
i have some websites hosted behind ELB on autoscaling group.
On my externals domain registrar (it can be namebay, ovh, whatever...) :
- i set CNAME www (www.domain.tld) to ELB name
- i set A (domain.tld) to my proxy server EC2+ip static then iptables redirects to my ELB.
- SSL certificates are distributed by EC2 instance autoscaling group behing ELB
everything works nearly perfectly but i find it very complicated to manage and i'd like a way to remove my proxy instance to manage everything on domain registrar
is there a better way to proceed ?
Can we confirm if **all** EC2 Classic Load Balancers will be retired after Aug 15, 2022?
Per this AWS Blog post https://aws.amazon.com/blogs/aws/ec2-classic-is-retiring-heres-how-to-prepare/ it says that the EC2 Classic Load Balancer will be retiring on August 15, 2022.
It also seems to indicate that there are 2 types of EC2 Classic Load Balancers. The first being the first generation. The second being the one with VPC.
I wasn't sure if both of those are going to be retired or just the first one.
I have projects using EC2 Classic Load Balancers with VPC so I want to make sure I'm ok and that I don't have to do any migration.
I have been using Terraform to deploy Elastic Beanstalk app and there seem to be an issue when I am trying to set custom ciphers for Classic Load Balancer. I have to repeat deployments by changing just the namespace from sslpolicy to TLSHighPolicy and revert back to sslpolicy before the custom ciphers appear.
Error I get look something like this
> failed Reason: Reference-Security-Policy attribute cannot be used together with attributes for ciphers and protocols. Either use the Reference-Security-Policy by itself or specify individual ciphers and protocols.
Settings I am using via Terraform
```
setting {
namespace = "aws:elb:policies:sslpolicy"
name = "SSLProtocols"
value = "Protocol-TLSv1.2,Server-Defined-Cipher-Order,ECDHE-ECDSA-AES256-GCM-SHA384,ECDHE-ECDSA-AES128-GCM-SHA256,ECDHE-RSA-AES256-GCM-SHA384,ECDHE-RSA-AES128-GCM-SHA256"
}
```
This works just fine after just manipulating with name and namespaces. This seems to be a bug at AWS's end. Please comment. Thanks.
Hello.
One of my environments is using a Classic Load Balancer. Sometimes, the queries I run in our database take more than just one minute, so I needed to increase the idle timeout of the Load Balancer (which is one minute by default). We followed the instructions and changed it to 3600 (s). However, I'm still getting the "connection closed" message after just one minute, so the new value of the idle timeout seems to have no consequence. Is there anything else I should be doing?
Is there someone who knows Spanish? I am very disappointed with the decision to switch to aws, the support is terrible, many things are very complicated, there is no CPanel where to solve the problems.