Member-only story
Making External HTTPS Requests Using AWS Lambda and Node.js
Logging and analyzing your data
Leveraging AWS Architecture
In a previous article we learned how to create a Node.js Lambda function and how to connect it with an HTTP API Gateway. Our Lambda looked something like this:
If you are just joining us, simply create a basic Lambda and connect it to a new HTTP API Gateway or follow this tutorial.
Step 1: Using CloudWatch
Chances are that you already visited the HTTP endpoint that triggers the Lambda function. But if you did not, just click on the link to your API Endpoint. After you do this, a log will automatically be generated for you. The great thing about AWS is that a lot of these things just work right out of the box for you. To see a log of this request that was made, go to the CloudWatch service from the AWS dashboard (you can search for CloudWatch from the services button in the header) and then click on the Log Groups subsection within Logs on the left pane. Once a request to your API endpoint was made, you should see the name of your lambda function appear on the list. Click on it and you will be taken to a bunch of log groups. If you have a small number that means that you had a small number of requests. This is what happens in my case. You can see here:
To search through all of these at once, click on the Search Log Group button. You can now see the logs of your request:
A great thing about this is that you are able to see how much you would be billed for. AWS gives us 1 million free requests per month and 400,000 GB-seconds of compute time per month, which is why we are using it. But if you did go over this limit, you can find out exactly how much money you…
