ALB limits

[drew222]

My understanding is that Amazon limits load balancers based on the sum of classic and application load balancers. This library seems to get the number of classic 'Active load balancers' on the 'ELB' service. Is it possible to sum together the classic and application load balancers values when checking against the 'Active load balancers' limit?

should be limit_type='AWS::ElasticLoadBalancingV2::LoadBalancer'

[jantman]

@drew222 According to the service limits documentation, there are separate limits for ELBs and ALBs, though that seems to conflict with what the Trusted Advisor documentation (see note below) says.

awslimitchecker currently only supports Classic load balancers, not ALBs.

As of today, there is a note on the Trusted Advisor FAQs page that says:

Note: The Active Load Balancers limit check is currently inaccurate. Although the limit applies to the total number of load balancers, the check counts only Classic Load Balancers and does not count Application Load Balancers.

As such, I'd prefer to wait on adding ALB support, since there is currently no way to programmatically retrieve an account's ALB limit; it's not available via any API, Trusted Advisor, or the EC2 Service Limits Report (the "Limits" tab on the EC2 Console). So we don't even know what AWS will call these limits, and there's no way for awslimitchecker to retrieve the current value short of each user tracking their limit increase requests and manually updating via a limit override.

For what it's worth, my employer has an Enterprise-level account, and we're trying to use that to push for an actual API call that exposes all EC2-related current limits.

[drew222]

Ahh okay, sounds like a waiting game. Thanks for the timely and detailed response!

[tamsky]

there is currently no way to programmatically retrieve an account's ALB limit; it's not available via any API, Trusted Advisor, or the ... ("Limits" tab on the EC2 Console).

Has this situation changed?

My Limits tab [1] shows ELB, ALB, and Target Group limits:

Which appears to derive from two different POST calls.

The ALB response data from https://console.aws.amazon.com/ec2/ecb?call=elbV2DescribeLoadBalancerAccountLimits? is:

{
  "limits": [
    {
      "name": "application-load-balancers",
      "max": "500"
    },
    {
      "name": "target-groups",
      "max": "400"
    },
    {
      "name": "targets-per-application-load-balancer",
      "max": "1000"
    },
    {
      "name": "listeners-per-application-load-balancer",
      "max": "10"
    },
    {
      "name": "rules-per-application-load-balancer",
      "max": "100"
    }
  ]
}

The ELB limits come from https://console.aws.amazon.com/ec2/ecb?call=describeLoadBalancerAccountLimits? which returns
{"limits":[{"max":"500","name":"classic-load-balancers"},{"max":"100","name":"classic-listeners"}]}

[1] https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#Limits:

[jantman]

Yes, it does appear the situation has changed. There are now ELB DescribeAccountLimits and ELBv2 DescribeAccountLimits API calls.

Unless something is broken, right now the EC2 Release Notes page doesn't show anything since 2014. So, as has been the case for years, nobody knows when new features are released. My employer has an Enterprise account and lack of API access to limits is one of the issues we've filed with our TAMs, and we haven't been told about this yet... According to the git history of the ELB API in botocore, the official Python API client (and library that awslimitchecker uses), the DescribeAccountLimits calls were added sometime between April 6 and May 11 of this year.

Thanks for bringing this to my attention, @tamsky. I'll update the labels on this issue and try to start work on it sometime this week.

[jantman]

This has been released in 0.11.0