Wsrtjtyk

I'm just trying to write a simple Lambda function to insert data into my MongoDB Atlas cluster. I've set the cluster to accept all incoming traffic (0.0.0.0/0) and confirmed that I can connect locally.

For AWS Lambda, I set up a VPC using the VPC wizard, and I gave my Lambda function a security role with full admin access. I set the timeout to 12 seconds, but I'm still getting the following error:

Response:

{

  "errorMessage": "2018-11-19T15:17:23.200Z 3048e1fd-ec0e-11e8-a03d-fb79584484c5 Task timed out after 11.01 seconds"

}



Request ID:

"3048e1fd-ec0e-11e8-a03d-fb79584484c5"



Function Logs:

START RequestId: 3048e1fd-ec0e-11e8-a03d-fb79584484c5 Version: $LATEST

2018-11-19T15:17:12.191Z    3048e1fd-ec0e-11e8-a03d-fb79584484c5    Calling MongoDB Atlas from AWS Lambda with event: {"address":{"street":"2 Avenue","zipcode":"10075","building":"1480","coord":[-73.9557413,40.7720266]},"borough":"Manhattan","cuisine":"Italian","grades":[{"date":"2014-10-01T00:00:00Z","grade":"A","score":11},{"date":"2014-01-16T00:00:00Z","grade":"B","score":17}],"name":"Vella","restaurant_id":"41704620"}

2018-11-19T15:17:12.208Z    3048e1fd-ec0e-11e8-a03d-fb79584484c5    => connecting to database

2018-11-19T15:17:12.248Z    3048e1fd-ec0e-11e8-a03d-fb79584484c5    (node:1) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.

END RequestId: 3048e1fd-ec0e-11e8-a03d-fb79584484c5

REPORT RequestId: 3048e1fd-ec0e-11e8-a03d-fb79584484c5  Duration: 11011.08 ms   Billed Duration: 11000 ms   Memory Size: 128 MB Max Memory Used: 29 MB  

2018-11-19T15:17:23.200Z 3048e1fd-ec0e-11e8-a03d-fb79584484c5 Task timed out after 11.01 seconds

The relevant part of my code for connecting is (with user and pass being the appropriate values):

const MongoClient = require('mongodb').MongoClient;

let atlas_connection_uri = "mongodb+srv://<user>:<pass>@restaurantcluster-2ylyf.gcp.mongodb.net/testdb"





let cachedDb = null;



exports.handler = (event, context, callback) => {

    var uri = atlas_connection_uri



    if (atlas_connection_uri != null) {

        processEvent(event, context, callback);

    } 

    else {

        atlas_connection_uri = uri;

        console.log('the Atlas connection string is ' + atlas_connection_uri);

        processEvent(event, context, callback);

    } 

};



function processEvent(event, context, callback) {

    console.log('Calling MongoDB Atlas from AWS Lambda with event: ' + JSON.stringify(event));

    var jsonContents = JSON.parse(JSON.stringify(event));



    //date conversion for grades array

    if(jsonContents.grades != null) {

        for(var i = 0, len=jsonContents.grades.length; i < len; i++) {



            jsonContents.grades[i].date = new Date();

        }

    }



    context.callbackWaitsForEmptyEventLoop = false;



    try {

        if (cachedDb == null) {

            console.log('=> connecting to database');

            MongoClient.connect(atlas_connection_uri, function (err, client) {

                cachedDb = client.db('testdb');

                return createDoc(cachedDb, jsonContents, callback);

            });

        }

        else {

            createDoc(cachedDb, jsonContents, callback);

        }

    }

    catch (err) {

        console.error('an error occurred', err);

    }

}

I suspect that something is going on with my VPC firewall/permissions/security group considering the fact that I can connect from my local machine, but I have no idea how that could be the case when I'm granting full admins privileges in my security role and I've set all outgoing VPC traffic to my public subnet.

I would appreciate any advice/help in solving this!

edit to provide more info:

The function console.logs '=> connecting to database' and then immediately times out at MongoClient.connect (confirmed by attempting to console.log directly after that).