mirror of
https://github.com/nickpoida/og-aws.git
synced 2025-02-14 19:02:00 +00:00
Merge pull request #551 from matthiasr/mr/xLB-limit-increases
Add note about ALB/CLB/NLB limit increases
This commit is contained in:
commit
fc5516ee98
1 changed files with 1 additions and 0 deletions
|
@ -1054,6 +1054,7 @@ Load Balancers
|
|||
- ❗CLBs and ALBs take time to scale up, it does not handle sudden spikes in traffic well. Therefore, if you anticipate a spike, you need to “pre-warm” the load balancer by gradually sending an increasing amount of traffic.
|
||||
- ❗Tune your healthchecks carefully — if you are too aggressive about deciding when to remove an instance and conservative about adding it back into the pool, the service that your load balancer is fronting may become inaccessible for seconds or minutes at a time. Be extra careful about this when an autoscaler is configured to terminate instances that are marked as being unhealthy by a managed load balancer.
|
||||
- ❗CLB HTTPS listeners don't support Server Name Indication (SNI). If you need SNI, you can work around this limitation by either providing a certificate with Subject Alternative Names (SANs) or by using TCP listeners and terminating SSL at your backend.
|
||||
- 🔸 There is a limit on the number of ALBs, CLBs and NLBs per region (separately). As of late 2017, the default limit for each is 20 per region. These limits can be easily raised for ALB and CLB, but AWS is quite reluctant to raise the limit on NLBs.
|
||||
|
||||
CLB
|
||||
---
|
||||
|
|
Loading…
Reference in a new issue