Skip to main content

Getting to know the Lambda Event Object

With any kind of http request, being it a simple web server or an api gateway, we will usually need to log different kind of information regarding the received request. But how can we do that with Lambda and how can we get all available information from it?

Thats when the event object comes in place. The API GATEWAY will send all information about the request encapsulated in the event object passing it as an argument to our lambda function, like this: 


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

};

The event object have the following nested objects as shown below:

  • 1. resource
  • 2. path
  • 3. httpMethod
  • 4. headers
  • 5. multiValueHeaders
  • 6. queryStringParameters
  • 7. multiValueQueryStringParameters
  • 8. pathParameters
  • 9. stageVariables
  • 10. requestContext
  • 11. body
  • 12. isBase64Encoded

{
   "resource": "/",
   "path": "/",
   "httpMethod": "GET",
   "headers": {},
   "multiValueHeaders":{
      "accept-encoding":[],
      "cookie":[],
      "Host":[],
      "User-Agent":[],
      "X-Amzn-Trace-Id":[],
      "X-Forwarded-For":[],
      "X-Forwarded-Port":[],
      "X-Forwarded-Proto":[],
      "x-real-ip":[]
   },
   "queryStringParameters":{},
   "multiValueQueryStringParameters":{},
   "pathParameters":null,
   "stageVariables":null,
   "requestContext":{
      "resourceId":"",
      "resourcePath":"",
      "httpMethod":"",
      "extendedRequestId":"",
      "requestTime":"",
      "path":"",
      "accountId":"",
      "protocol":"",
      "stage":"",
      "requestTimeEpoch":,
      "requestId":"",
      "identity":{
         "cognitoIdentityPoolId":null,
         "accountId":null,
         "cognitoIdentityId":null,
         "caller":null,
         "sourceIp":"",
         "accessKey":null,
         "cognitoAuthenticationType":null,
         "cognitoAuthenticationProvider":null,
         "userArn":null,
         "userAgent":"",
         "user":null
      },
      "body": null,
      "isBase64Encoded"
   }
}
Labels:

Comments

Post a Comment

Popular posts from this blog

How to use Splunk SPL commands to write better queries - Part I

Introduction As a software engineer, we are quite used to deal with logs in our daily lives, but in addition to ensuring that the necessary logs are being sent by the application itself or through a service mesh, we often have to go a little further and interact with some log tool to extract more meaningful data. This post is inspired by a problem I had to solve for a client who uses Splunk as their main data analysis tool and this is the first in a series of articles where we will delve deeper and learn how to use different Splunk commands. Running Splunk with Docker To run Splunk with docker, just run the following command: docker run -d —rm -p 8000:8000 -e SPLUNK_START_ARGS=--accept-license -e SPLUNK_PASSWORD=SOME_PASSWORD --name splunk splunk/splunk:latest Sample Data We are going to use the sample data provided by Splunk. You can find more information and download the zip file from their web site . How does it work? In order to be able to interact with Splunk t...
Post a Comment
Read more

How to become a Blockchain developer and write your first Smart Contract

Introduction This is an introductory article to help you understanding the tools and frameworks needed so that you can know from where and how to start creating your own Smart Contracts. In this post I will give you an overview of the tools, frameworks, libraries and languages used to create a Smart Contract in the Ethereum Blockchain . In the second part of this article, we are going to see how to create a Smart Contracts using Solidity and ee are also going to see how to run a Blockchain locally using Ganache , so that you can deploy, interact and test your Smart Contract in your local development environment. According to a definition from the Wikipedia website: A blockchain is a decentralized, distributed, and often public, digital ledger consisting of records called blocks that are used to record transactions across many computers so that any involved block cannot be altered retroactively, without the alteration of all subsequent blocks.. What do you need to know? T...
Post a Comment
Read more

How to run OPA in Docker

From the introduction of the openpolicyagent.org site: OPA generates policy decisions by evaluating the query input against policies and data. In this post i am going to show you an easy and fast way to test your policies by running OPA in Docker. First, make sure you have already installed Docker and have it running: docker ps Inside your choosen directory, create two files. One called input.json file for your system representation and one file called example.rego for your rego policy rules. Add the following content to your json file: Add the following content for the example.rego: Each violation block represents the rule that you want to validate your system against. The first violation block checks if any of the system servers have the http protocol in it. If that is the case, the server id is added to the array. In the same way, the second violation block checks for the servers that have the telnet protocol in it and if it finds a match the server id is also...
Post a Comment
Read more