Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Error when trying to send SNS

Open
  • Is something wrong?
#203 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, javascript, node.js
Domain
backend, cloud

Research direction

Start with the Lambda entry points shown in index.js around lines 1377, 1397, and 1433, then reproduce the S3 upload with the wrong format while checking the CloudWatch logs. Compare the SNS failure under the reported Lambda runtimes and trace the callback error path. Done means the notification path works or the runtime compatibility limitation is documented with a reproducible cause.

Written by the indexing model from the issue text.

Description

Hi,

I just deployed 2.7.0 and uploaded a test file to S3 bucket with wrong format to test the notification, but it seems lambda function failed when trying to send SNS. I wonder if this is caused by incompatibility with runtime environment? Got the same error when using nodejs10.x and nodejs12.x. CloudWatch log:

{
    "errorType": "Error",
    "errorMessage": "error",
    "stack": [
        "Error: error",
        "    at _homogeneousError (/var/runtime/CallbackContext.js:13:12)",
        "    at postError (/var/runtime/CallbackContext.js:30:51)",
        "    at done (/var/runtime/CallbackContext.js:57:7)",
        "    at Object.done (/var/runtime/CallbackContext.js:105:16)",
        "    at /var/task/index.js:1377:37",
        "    at /var/task/index.js:1433:13",
        "    at /var/task/node_modules/async/dist/async.js:473:16",
        "    at next (/var/task/node_modules/async/dist/async.js:5329:29)",
        "    at /var/task/node_modules/async/dist/async.js:969:16",
        "    at Response.<anonymous> (/var/task/index.js:1397:13)"
    ]
}

and on nodejs8.10:

{
    "errorMessage": "error"
}

Since nodejs8.10 is approaching end of life: https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html

0.10 have long deprecated and is no longer available in AWS Lambda, I wonder if there is any plan for supporting 10.x and 12.x?

Dominant language
JavaScript
Stars
595
Forks
161
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from awslabs/aws-lambda-redshift-loader

All issues in awslabs/aws-lambda-redshift-loader

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.