All good.
RE: VPC…maybe the network connections being setup cause the issue???
Oh interesting, that makes more sense now. With VPC the current lambdas are creating an ENI card for each lambda function. So the rate limit is reached much more quickly. The extra ec2 API calls to create the ENIs don’t happen in non-vpc.
Recently, AWS announced Lambda VPC speed improvements support. It should also help because only a few ENIs will be created instead of one for each function. Details:
- Lambda + Aurora Serverless - #5 by tung - Jets - BoltOps Community
- Announcing improved VPC networking for AWS Lambda functions | AWS Compute Blog
- https://rubyonjets.com/docs/considerations/vpc/
Wondering if after the Lambda VPC speed improvements are fully rolled out, the rate limit issues you’re seeing will also go away. AWS says they are partially rolling it out already on some AWS accounts and will be eventually fully rolled out. No definite timeframe though.