What exactly does use_nested_table_rate_limiting do in the AWS plugin? It looks like the nested table concurrency defaults to 5 now, but use_nested_table_rate_limiting defaults to false. What is the difference in concurrency between true and false? GitHub Commit
When use_nested_table_rate_limiting is enabled, nested tables cannot use the entire concurrency pool that is allocated to them. We restrict each nested table to a maximum of 5 concurrent instances that are resolving in parallel. For top-level tables that generate a lot of data, like aws_stepfunctions_executions, this means that we will only resolve 5 instances of the nested table aws_stepfunctions_map_runs at a time.
I thought this was the default behavior. But in AWS it defaults to false?
You are correct, it is the default behavior in the scheduler. I think that it was intended for the attribute to be removed from the AWS plugin. We will investigate it.