Should boto3 automatically batch requests to avoid FilterLimitExceeded?

[nchammas]

If you do something like this

ec2.instances.filter(
    Filters=[
        {'Name': 'instance-id', 'Values': [i['InstanceId'] for i in instances]}
    ]))

where len(instances) > 200, you will get the following error:

An error occurred (FilterLimitExceeded) when calling the DescribeInstances operation:
The maximum number of filter values specified on a single call is 200

This seems like something boto3 should handle for the user, but I'm not sure. Should boto3 be responsible for batching requests where needed, like in this case, to avoid FilterLimitExceeded, or is that on us?

Related:

• Flintrock doesn't support more than 200 instances nchammas/flintrock#193

[JordonPhillips]

We typically don't do automatic batch handling unless explicitly called out. The only cases I'm aware of are the dynamodb batch get/write operations. For now you'll have to manually handle that.

It would be great to have this feature more generally, so marking as a feature request.

[larroy]

I'm affected

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than two years. We encourage you to check if this is still an issue in the latest release. Because it has been longer than two years since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment to prevent automatic closure, or if the issue is already closed, please feel free to reopen it.