从Nodejs中的Dynamodb Steam调用AWS Lambda

Question

当我尝试从AWS控制台运行lambda函数时，代码工作正常。由于我想仅在添加了新的Dynamo DB记录时运行特定代码，因此我想从dymanoDB流插入事件中运行lambda函数。我尝试了以下代码，似乎lambda没有调用。

serverless.yml中的权限

  - Effect: "Allow"
    Action:
      - "lambda:InvokeFunction"
    Resource: 
      - "*"

dynamoDB流代码

 

exports.main = async (event) => {
    const records = event.Records.filter((record) => {
        if (record.eventName.toUpperCase() === "INSERT") {
            const recordType = record.dynamodb.NewImage.type.S;

            if (recordType.toUpperCase() === "TRA") {
                 // here I capture the value for the arguments. They work fine
                 inkvokeTraLamda(keyword, key, tag);
            }  
        }
    });
};

const AWS = require("aws-sdk");
const lambda = new AWS.Lambda({ region: "us-west-1" });
exports.inkvokeTraLamda = async function invoke(
    keyword,
    key,
    tag
) {
    const playload = {
        keyword,
        key,
        tag,
    };

    const LambdaPromise = (params) => lambda.invoke(params).promise();

    const resp = await LambdaPromise(params);
    console.log(resp);
    return resp;  
};

我将非常感谢你的指导。

Answer 1

而不是告诉一个lambda函数调用另一个。配置相关的Lambda函数以侦听DynamoDB流。因此，您的侦听器Lambda会将其添加到其事件配置中。

  events:
  - stream:
      type: dynamodb
      batchSize: 1
      # INFO: Batch Window size in seconds allows you to wait as long as 300s to build a batch before invoking a function.
      # Now, a function is invoked when one of the following conditions is met: the payload size reaches 6MB, the Batch Window reaches its maximum value, or the Batch Size reaches its maximum value.
      # With Batch Window, you can increase the average number of records passed to the function with each invocation.
      batchWindow: 5
      # This gives the option to recursively split the failed batch and retry on a smaller subset of records, eventually isolating the metadata causing the error.
      bisectBatchOnFunctionError: true
      maximumRetryAttempts: 3
      maximumRecordAgeInSeconds: 120

      arn:
        Fn::GetAtt:
          - <TableName>
          - <TableStreamArn>

一旦插入了什么，您的第二个代码段就会响应。第三个片段似乎与DB流无关。