mod5_Issue sending data through AWS Function

[uznab16]

I'm running into issues with my lambda function. When I test in AWS, I get the follow message:

Status: Succeeded
Test Event Name: test

Response:
{
"statusCode": 500,
"body": "{"error": "Received error: 'body'. Check the AWS Lambda logs (On the function page, navigate to 'test' then 'CloudWatch Logs Live Tail', select the log group, click start, and then run the request again to monitor the full error)"}"
}

Function Logs:
START RequestId: cf9539e4-2fc8-4b6c-9244-dbfc06287716 Version: $LATEST
{'key1': 'value1', 'key2': 'value2', 'key3': 'value3'}
'body'
File "/var/task/lambda_function.py", line 30, in lambda_handler
payload = json.loads(event["body"])

END RequestId: cf9539e4-2fc8-4b6c-9244-dbfc06287716
REPORT RequestId: cf9539e4-2fc8-4b6c-9244-dbfc06287716 Duration: 3000.00 ms Billed Duration: 3000 ms Memory Size: 128 MB Max Memory Used: 60 MB

When I use mongodb_credentials_test.py in my codespaces, I am able to connect to MongoDB fine, but I get the same error for the lambda function that I cannot figure out my way around:

Pinged your deployment. You successfully connected to MongoDB!
Inserted a test document into the horn collection.
Found the test document in the horn collection.
Deleted the test document from the horn collection.
Traceback (most recent call last):
File "/workspaces/5-data-logging-uznab16-1/mongodb_credentials_test.py", line 90, in
test_lambda_function_url()
File "/workspaces/5-data-logging-uznab16-1/mongodb_credentials_test.py", line 83, in test_lambda_function_url
response.status_code == 200
AssertionError: Received status code 502 and message Internal Server Error. Failed to add {'course_id': 'animated-giraffe'} to giraffe:horn via https://ygndu3usyaca365el7iarwchl40bxpjr.lambda-url.us-east-2.on.aws/.

If it helps, I noticed in a different thread that user cjbrew had slightly different error messages for both of these:
(1) they did not have
"File "/var/task/lambda_function.py", line 30, in lambda_handler
payload = json.loads(event["body"])" AND
(2) in their mongodb_credentials_test.py error message, they have something like "UoT_SDL_DB_Main:Tutorial Data" instead of the Function URL like I do

[sgbaird]

Could you include a link to your assignment repo?

[sgbaird]

Similarly @wavyparticle, if you have anything to add

[sgbaird]

@uznab16 I verified with a from-scratch MongoDB instance and AWS instance while following the setup instructions that I see the same behavior you mention in #160 (comment).

I started debugging, and I think I have it. Copying a few snippets:

• For testing in the AWS console, use a test event that mimics the Function URL structure:

  {
    "body": "{\"database\": \"test-db\", \"collection\": \"test-collection\", \"document\": {\"course_id\": \"test\"}}"
  }

• Alternatively, test via the actual Function URL using curl or your insert.py script.

Once updated, redeploy the function and re-run the tests. The Lambda should now connect to MongoDB correctly. If issues persist, check the CloudWatch logs for more details on the error.

Then, once I used the above (copy the JSON verbatim), I saw that it was timing out. See below:

The AWS Lambda function is timing out after 3 seconds (the default timeout), likely due to the initial MongoDB connection taking time or a slow network.

Steps to Fix:

1. Increase the Timeout:

   • In the AWS Lambda console, go to Configuration > General configuration > Edit.
   • Set Timeout to 30 seconds (or more if needed).
   • Save the changes.

2. Redeploy and Test:

   • Redeploy the function if prompted.
   • Test again using the correct test event or your insert.py script.

This should resolve the timeout. If the issue persists, check CloudWatch logs for connection errors or optimize the MongoDB client initialization (e.g., ensure the Atlas URI is correct and the user has proper permissions).

Once I increased the timeout, it was working on insert.py.

Unfortunately, the README instructions and the lambda function generated by the colab notebook seem to be at odds with each other. Here is the quick manual fix I made, though I will need to go in and update these to be consistent with each other.

import os
import json
from pymongo import MongoClient


# atlas_uri as copy-pasted from MongoDB
atlas_uri = "<insert your full filled out one here>"

client = MongoClient(host=atlas_uri)


def lambda_handler(event, context):
    try:
        print(event)
        payload = json.loads(event["body"])

        document = payload["document"]
        print(document)

        # You can restrict the MongoDB user to only access certain databases or
        # collections, but if you're worried about potential risk in accessing other
        # collections, an alternative to what's shown below is to hardcode the db
        # and collection names into the AWS Lambda function (as-is, it receives
        # these names)
        db_name = payload["database"]
        collection_name = payload["collection"]

        db = client[db_name]
        collection = db[collection_name]

        # Insert document
        print(f"sending document to {db_name}:{collection_name}")
        result = collection.insert_one(document)

        return {
            "statusCode": 200,
            "body": json.dumps({"message": f"Document inserted successfully to {db_name}:{collection_name} with id {result.inserted_id}"}),
        }
    except Exception as e:
        # This helps with providing some meaningful feedback instead of e.g., "Internal Server Error" when invoking the Python function
        print(e)
        return {
            "statusCode": 500,
            "body": json.dumps({"error": f"Received error: {str(e)}. Check the AWS Lambda logs (On the function page, navigate to 'test' then 'CloudWatch Logs Live Tail', select the log group, click start, and then run the request again to monitor the full error)"}),
        }

Could you give this a try?

EDIT: just pushed a new version of the lambda prep notebook

[uznab16]

@sgbaird While I still have access to Github, my course enrollment has expired, so I can no longer access the course page to do quizzes or assignments. I may try to go back and apply what you've provided, but it will take me some because need to refresh my memory on the module.

[sgbaird]

Could you send me an email? (Email on my GitHub profile)

[cendanaf]

Hey has this been resolved?

Increasing the timeout to 30 seconds fixed the 502 error but now I am getting a 500 error as well

[uznab16]

I didn't attempt it. I wasn't able to extend my course allowance due to some logistics. Thanks for your help though.

…

________________________________ From: cendanaf ***@***.***> Sent: Monday, February 9, 2026 8:50 AM To: AccelerationConsortium/ac-microcourses ***@***.***> Cc: Nwabara, Uzoma ***@***.***>; Mention ***@***.***> Subject: Re: [AccelerationConsortium/ac-microcourses] mod5_Issue sending data through AWS Function (Discussion #160) Hey has this been resolved? Increasing the timeout to 30 seconds fixed the 502 error but now I am getting a 500 error as well — Reply to this email directly, view it on GitHub<#160 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BLZHDFS4S3WNLKUWYZU5CP34LCNB5AVCNFSM6AAAAAB3UME7BSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZUGQ4TIMQ>. You are receiving this because you were mentioned.Message ID: ***@***.***> This e-mail may contain privileged or confidential information. If you are not the intended recipient: (1) you may not disclose, use, distribute, copy or rely upon this message or attachment(s); and (2) please notify the sender by reply e-mail, and then delete this message and its attachment(s). Underwriters Laboratories Inc. and its affiliates disclaim all liability for any errors, omissions, corruption or virus in this message or any attachments.