- 最新
- 投票最多
- 评论最多
Could someone explain to me if I can predict the total amount of ENIs assigned to an ALB when deployed in all availability zones?
Define "predict" and "when deployed".
Short answer is No.
ALB size for users is expressed in LCUs rather than individual nodes/ENIs. Corresponding CW metric is ConsumedLCUs. You can't say upfront whether N number of LCUs will always be equivalent to M number of ENIs.
It may not even be 1 ENI per AZ when provisioned in case of pre-warming. I had a handful of such cases.
https://repost.aws/questions/QUhvpfhsDsSZKRvoLOyWMRkQ/alb-pre-warming.
I recommend reaching out to AWS technical support if you have a question about specific ALB.
AWS offers "Public IP Insights" tool at no cost to track public IPv4 usage. This tool covers ALBs. Here is the reference to AWS doc: https://docs.aws.amazon.com/vpc/latest/ipam/view-public-ip-insights.html
Through the use of Public IP Insights, I came to the conclusion that some ALBs have more ENIs provisioned. Hence, this is not really an answer to my question. Maybe I should have made it more clear that I executed my analysis via this tool.
Those ENIs are created to allow ALB to talk to targets in your VPC. Minimum configuration is to have an ENI per AZ where ALB is deployed (2 or more) but when there is more traffic, ALB can scale more load balancer instances (not to be mixed with auto-scaling of target instances). As one ENI can be attached to single instances, more ENIs are created too.
Here is another question & answer about load balancer scaling that could be helpful
相关内容
- 已提问 10 个月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
Thanks for the quick response. Most of the our shared load balancers contain several applications, where the LCU count is below 1 LCU (avg. of 0.6). This specific load balancer had 5 ENIs assigned which scaled-in back to 3 and I did not cross-reference this with the LCU count, which I will do in the future.