Although Lambda Layers can be used to push stale package references into externalized layers and let Lambda use these from the layers, we might also want to have our Custom Class libraries which might contain business logic to work in the same way, so that they could be reused in other lambda functions as well. For this, we make use of Nuget packages to pack and store our libraries. Learn how to implement this and deploy our libraries in Layers.
AWS Lambda Layers were introduced on top of the Lambda deployment stack for cloud applications. They are added to provide support for reusable components and in an attempt to reduce the coldstart issues of the Lambda services.
let's go one step ahead and look at how we can deploy this API we have built into an AWS Lambda and access it using API Gateway.
In this getting started article, let's talk about how we can develop a simple RESTful API which performs basic CRUD operations (Create, Retrieve, Update and Delete) on table data by connecting and integrating with MySql database.
In this article, let's talk about another such simple Flow - which can be used for user authentication. It is called as the Resource Owner Password Credentials Grant (ROPC) flow.
In this article, let's look at Implementing ClientCredentials auth flow, which is one of the basic auth flows used for securing and granting access to API resources to clients which possess an access_token issued by the configured TokenServer safeguarding the API.
In this article, let's get to know in detail about how Token servers work and how we create and secure our AspNetCore APIs with IdentityServer4.
In a previous article we have seen how we can provide a multitude of options of concrete implementations and vary dynamically using a Factory pattern. And this is let's look at how can maintain a factory of factories which is called as an Abstract Factory.
In this article, let's look at how the UserPool created is used in an actual application perspective - how we can secure an application using UserPool created in AWS Cognito. The expectation is that when a user authenticated in AWS Cognito and obtained a Token tries to access the API using the Token, the API must be able to validate the Token for its authenticity and let the user pass or deny access.
Understanding AWS Cognito and Setting up User Pools for Authentication