Skip to main content

Getting to know the S3 Event Object

In this post i am going to show you how you can get into the content of the file that trigged your lambda.

As we have seen in the previous post, the event object is passed as an argument to our lambda function, like this:


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

};

When you place a trigger on a Lambda function based on a S3 event, S3 will pass all the context information that you need inside of the event object. In this case, our lambda will be trigged by an S3 event and the event object that will be passed to it will have a Record property with an array of objects inside of it like is shown below:

{
   "event":{
      "Records":[
         {
            "eventVersion":"2.0",
            "eventSource":"aws:s3",
            "awsRegion":"us-east-1",
            "eventTime":"2018-09-22T14:25:20.411Z",
            "eventName":"ObjectCreated:Put",
            "userIdentity":{
               "principalId":""
            },
            "requestParameters":{
               "sourceIPAddress":""
            },
            "responseElements":{
               "x-amz-request-id":"",
               "x-amz-id-2":""
            },
            "s3":{
               "s3SchemaVersion":"1.0",
               "configurationId":"",
               "bucket":{
                  "name":"",
                  "ownerIdentity":{
                     "principalId":""
                  },
                  "arn":""
               },
               "object":{
                  "key":"",
                  "size":226,
                  "eTag":"",
                  "versionId":"",
                  "sequencer":""
               }
            }
         }
      ]
   }
}

You will want to pay a special attention to the S3 property here. This property contains an object that have two important properties for us, the bucket and the key. Using those information, that is, the bucket name and the file name, that we can get into the content of our S3 file like this:


var bucket = event.Records[0].s3.bucket.name;
var file = event.Records[0].s3.object.key;

var params = {
  Bucket: bucket, 
  Key: file
 };
 s3.getObject(params, function(err, data) {
   if (err) console.log(err, err.stack);
   else     console.log(JSON.parse(data.Body.toString('utf-8'))); 
 });

This will return a data object containing your object properties, assuming you hava a json object on it. The JSON.parse() here is used to convert it back to an object, instead of having it as string.

Comments

Popular posts from this blog

Understanding RabbitMQ

Introduction RabbitMQ is a centralized message broker based on the AMQP (Advanced Message Queuing Protocol) protocol, acting as a Middleware between Producers and Consumers of different systems. In a message system, Publishers sends a message to a message broker where messages are consumed some time later by one or more Subscribers. By introducing a message brokeer between systems we are decoupling the sender application from the receiver. In this case the service that is responsible for sending or publishing the message does not need to know about any other service. All it needs to care about is the message and its format. With a message system you send a message to a message broker first and when the consumers or listeners of it become online they can start consuming from the message queue. This means you can keep sending messages without even care if the other application is online or if they had any failures. RabbitMQ Architecture Exchange, queue and bindings are the ...

A Retrospective board to call your own made with React, GraphQL and MongoDB

Introduction I have been working in a project to enable anyone to fork and run a retrospective board in its own server. I have created 2 (two) projects: one for the UI with React and GraphQL using Apollo client and one for the GraphQL server also using Apollo (Server) and MongoDB for the database. In the following sections I am going to walk you through the steps and explain how to run both projects. Main features The board main features: - History of your past iteractions saved in the Mongo database - Easy url link format to quick access any past iteractions - Automatically add action items as last action items in the new board - Quick move items to Action Items Coming next You can fork the React UI from the following GitHub repo: - Support for multiple teams - Authentication - Subscriptions (pub/sub) Code Repo You can fork the React UI from the following GitHub repo: React Retrospective UI You can fork the GraphQL Server from the following GitHub rep...

Simple, quick and easy steps to run an Oracle Database in your development environment using Docker without overloading your machine

Introduction In our development environment, besides being easy and fast to use, above all, we need a lightweight version of it to run locally, right? I have tested different Oracle images and this was the option that best work for me. In this post i will show you how you can run the Oracle Database Express Edition version on your local machine quickly and easily and also how to connect to it using Oracle SQL Developer IDE and SQL*Plus. How to do it Basically we just need two simple steps to get our Oracle database running on our local environment. First we need to login to the Oracle Container Registry so we can pull the image from it and then we just need to run it in a container. You can find more information by going to the Oracle Container Registry , under the "Browse Containers", click into Database and next click in the express Repository for the Oracle Database Express Edition. I am going to skip the docker pull step, because docker run will do it for us ...