Browse through the questions and answers listed below or filter and sort to narrow down your results.
Will the "TargetConnectionErrorCount" be counted even if there are two servers in the target group and one cannot respond?
I want to ask the case:
I have 2 Webservers in 1 target group. I think that if the connection from ALB to only 1 between/among targets have something wrong, the TargetConnectionErrorCount will be count.
When testing, I make one of my webserver become can not connect (Request timed out) by changing the Security group. I think that TargetConnectionErrorCount will be counted here, but it not. I have to make all of my targets become unhealthy to see the TargetConnectionErrorCount be count (see the attached images)
Is it right that only when all the target servers in the target group healthcheck fail will the TargetConnectionErrorCount metrics be counted?
Attached image here: https://live.staticflickr.com/65535/52061333803_d622b9a25c_b.jpg
Accepted AnswerElastic Load Balancing
1
answers
0
votes
8
views
asked 11 days ago
1
answers
0
votes
6
views
asked a month ago
Q: What’s the difference between “an ALB configured with pass-through traffic without TLS offload” vs “a NLB configured to pass-through traffic without TLS offload” ?
I know ALB can be configured to just pass-through the packet without TLS offloading. In that case, because payload is encrypted, then ALB only get limited access to the payload to do any dynamic routing (content based sticky session, etc).
My question is, in this case, is there any difference if I use a NLB without TLS offloading? Does ALB without TLS Offloading functionally the same as NLB without TLS Offloading?
Accepted AnswerElastic Load Balancing
1
answers
0
votes
4
views
asked a month ago
1
answers
0
votes
2
views
asked 2 months ago
TLS 1.3 support for NLB
I am trying to configure my ALB to allow TLS 1.3. I read the article that this feature is available with the security policy in bold below:
https://aws.amazon.com/about-aws/whats-new/2021/10/aws-network-load-balancer-supports-tls-1-3/
```
Elastic Load Balancing provides the following security policies for Network Load Balancers:
ELBSecurityPolicy-TLS13-1-2-2021-06
ELBSecurityPolicy-TLS13-1-2-Res-2021-06
etc
etc
```
The newest security policy I am offered is "ELBSecurityPolicy-FS-1-2-Res-2020-10"
I may be missing a key concept with load balancers and Listener security policies and would appreciate any help. It's an Application Load Balancer, HTTPS/443 chosen as the only listener.
Accepted AnswerElastic Load Balancing
1
answers
1
votes
11
views
asked 2 months ago
3
answers
0
votes
8
views
asked 4 months ago
0
answers
0
votes
7
views
asked 4 months ago
AWSALB and AWSALBCORS are 3rd party cookies in web
Our services are called from the websites of our customers.
We use ALB to balance and forward requests to the final targets.
Some of our services require session stickiness.
AWSALB* cookies are created in our own domain, so they are considered 3rd party cookies (which they are, in fact).
However, this is huge a problem, since we cannot serve clients with 3rd party cookies blocked in their browsers.
How can we handle this?
Is there a way to keep session stickiness without those cookies?
Thanks in advance.
Accepted AnswerElastic Load Balancing
1
answers
0
votes
185
views
asked 4 months ago