aws-sdk-js

I have to translate the DDB stream message into normal json type. For this I am using unmarshalleddata = aws.DynamoDB.Converter.unmarshall(result.NewImage); where result.NewImage is { carrier: { S: 'SPRING' }, partnerTransactionId: { S: 'a87ce47a46d7416586e0ece39f706d48' }, shipmentId: { S: 'SPRING2200419561404932' }, compressedShipmentPayload: { B: 'H4sIAAAAAAAAAO1b+ZPiRrL+Vzr4tb3TkrgaR7yIFWdDI3FJHHqxMSEkIQQ6aB1cjvnfX2ZVAoJur+1963hHeMaepirry8r6MisrRZd+KVhRHDu+mXpR2LULPxeWZkkwq2ZVFEulklWumo65sqt2tVhbrZzqqlL4qWBlfprFTiOyHQA44d86dejdmXEaOjEqqdSqr

Recently I am working on a project with Amazon Lambda. I created a lambda function as following var AWS = require ('aws-sdk'); exports.handler = (event, context, callback) => { // TODO implement var connect = new AWS.Connect({apiVersion: '2017-08-08'}); var params = { InstanceId: '' /* required */ }; connect.getCurrentMetricData(params, function(err, data) { if (err) console.log(err, err.stack); // an error occurred else { const response = { statusCode: 200, body: JSON.stringify(data) }; callback(null, data); } // successful response }); // const response = { // statusCode: 200, // body: JSON

I'm using the AWS Javascript SDK and I'm following the tutorial on how to send an SQS message. I'm basically following the AWS tutorial which has an example of the sendMessage as follows: sqs.sendMessage(params, function(err, data) { if (err) { console.log("Error", err); } else { console.log("Success", data.MessageId); } }); So the sendMessage function uses a callback function to output whether the operation was successful or not. Instead of printing to the console I want to return a variable, but every value I set is only visible within the callback function, even global variables like window

I'm using AWS SDK for Javascript (Node.js) to read data from a DynamoDB table. The auto scaling feature does a great job during most of the time and the consumed Read Capacity Units (RCU) are really low most part of the day. However, there's a programmed job that is executed around midnight which consumes about 10x the provisioned RCU and since the auto scaling takes some time to adjust the capacity, there are a lot of throttled read requests. Furthermore, I suspect my requests are not being completed (though I can't find any exceptions in my error log). In order to handle this situation, I've