We are currently running our AWS Lambda's in a VPC due to an earlier architectural decision.
We are also using MongoDB Atlas and a peering connection setup between the VPC and Atlas. This obviously is causing longer cold starts with the need of setting up the ENI.
I'm looking to cut this down by moving our database within the same VPC but want to do a sanity check if this is even possible.
Current flow is API Gateway -> AWS Lambda on VPC using Serverless Framework <- PEERING CONNECTION -> MongoDB Atlas for datastore.
If we run something like DocumentDB or DynamoDB within the same VPC as the VPC that is running our AWS Lambdas, will we still encounter the ENI creation delay and limits?
During a previous AWS Re:invent event there was talk of improving this by pooling the ENI's but we have not received any update about this going live yet, is there an update this?