Intermittent 'SSL connection has been closed unexpectedly' in lambda with provisioned concurrency while reading from Postgres Aurora DB using RDS proxy

We have a lambda function for which provisioned conurrency =1 is enabled. We insert records in Postgres Aurora RDS using this lambda. We are connecting to RDS proxy endpoint to connect to db . The db object creation is done in below manner :

@staticmethod
    def init_database_dao():
        if Dao._db_connection_dao is None:
            _logger.info(msg=f"creating db connection , singleton")
            ConnectionProvider._db_connection_metadata_dao = MetadataDao()  // inside MetadataDao we are calling postgres.connect()
        else:
            _logger.info(msg=f"refreshing connection for MetadataDao singleton")
            DatabaseConnectionProvider._db_connection_metadata_dao.reset_if_cursor_or_conn_is_none()
        return DatabaseConnectionProvider._db_connection_metadata_dao

We getting 'SSL connection has been closed unexpectedly' while executing SELECT query once in few hours (can be in 2 hours ,sometimes in 6 hours). We have handled this Postgres Operational Error by resetting the connection in code and retrying and it works. Not able to find the root cause of this error. we are using RDS proxy, we increased the idle client timeout of the proxy from 30 mins to 60 mins , we observed the frequency of this error has reduced. Also we are using the same db for other lambda (with same db object creation implementation) , those lambdas dont have provisioned concurrency enabled, we never encountered SSL connection closed error in those lambdas, Is it somewhat related to the lambda always warmed up(provisioned concurrency) and the connection getting shutup or destroyed. Any suggestions to get rid of this error? Note : The lambda with provisioned concurrency is the entry point of the application . In this lambda we are getting connection object, then reading from db and inserting into db .Once it is executed the other lambdas are triggered .