Secure Amazon API Gateway REST API using Lambda Authorizer [Written in C# and .NET Core 3.1]

In this video, I am going to walk through how we can create a .NET Core 3.1 Lambda authorizer and configure it in Amazon API Gateway to enable a secure authenticated API.

Previous video on Lambda and API Gateway:

00:00:10 - What is Lambda Authorizer
00:00:40 - Explain the request flow through a diagram
00:02:00 - .NET Core 3.1 Amazon Lambda for handling the API Gateway requests
00:02:50 - NuGet package needed for the API Gateway requests handler lambda
00:03:30 - Create a new REST API in API Gateway and attach the Amazon lambda request handler
00:04:22 - Deploy the newly created API in the Amazon API Gateway
00:04:38 - Test the newly created API in the Amazon API Gateway
00:05:12 - Walking through the Authorizers menu in the API Gateway
00:05:30 - Walking through the .NET Core 3.1 Amazon Lambda Authorizer function
00:07:00 - Explanation of the IAMPolicyStatement object and its consequences
00:07:32 - Explanation of all the parts of the Resource property of the IAMPolicyStatement
00:08:32 - Publishing lambda to AWS cloud
00:08:52 - Configure AWS API Gateway Authorizer with the newly created Amazon Lambda function
00:09:50 - Test the Authorizer using AWS Console
00:10:22 - Configure the API Resource with the Authorizer to enable authentication
00:11:06 - Test the API with the Authorizer
00:11:20 - Test using Postman passing the authentication header

[ranjitpanigrahi]

If I don't want to hard to the api gateway url, what options do I have?

[KrishnaKrish]

A friendly reminder that aws api gateway timeout is 29seconds. If your lambda runs for more than 29s look for alternatives like SQS or invoking lambda which will bypass this 29s limit. However lambda's timeout can be set upto 15mins