1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
It would help a lot if you could describe more about what you're trying to do and what is in your environment. For example what targets are you using for the load balancer (EC2 or Lambda - I assume EC2) and what type of load balancer (I assume Application Load Balancer but that may not be the case). Also: Are you getting an error message? If so, what is it? Is it being generated by the load balancer or the target?
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
Thanks for your post. It was generated from the load balancer side and not the target.
I finally figured out that the AWS load balancer was just routing traffic to an internal VM where nginx was installed.. so I logged into the VM and changed the nginx configuration in /etc/nginx/nginx.conf to add the line in the http section:
then reloaded the new nginx configuration using the command: nginx -s reload ... and the http error 413 no longer appeared.