Best practices for connection handling in AWS Lambda environment

Can anyone suggest best practices to use when developing AWS lambda functions (.NET core). Our main concern is MongoClient does not provide connection close method so this might leave too many opened connections and cluster might run into resource problems.