Integrate an API with lambda - Part 3

Let us look at request validation features in API gateway
when user requests for an end point (resource) we could perform few validations before processing the request. For example, the end point might require one or more of the below fields

  • query parameters
  • path parameters
  •  header
  • body
API gateway provides validation for these fields.

There are multiple options available here. Default is none. Validate body is used if the request has a payload and that needs to be schema validated before processing. We could also use the option that validates for required query string parameters and headers. Names for the parameter that are applicable can be provided in the section as shown below


If the parameters need to be part of the cache we need to enable caching so that parameter becomes part of the cache key. Also the request body section will need the name of the model and the content type of the body. We need to create models in the section below first and then refresh the above section to select the required model.



Comments

Post a Comment

Popular posts from this blog

Integrate an API with lambda - Part 5

Image
In this part of the blog we will cover the section Integration Response  in detail. This is where we configuration how the response needs to be mapped. On clicking the  details we get a similar screen In here we could add multiple integration responses. This is a very important section for output error code mapping.  If we intend to capture some keyword coming from backend we can use regex expression to filter response and handle the conversion. For example, we could expression .*exception*. to filter responses which has exception occurring any where and map it to error code like 500. Below screenshots shows the steps involved in achieving this.
Read more

Custom authorizer

Creating custom authorizer using SAM AWSTemplateFormatVersion: '2010-09-09' Transform: AWS::Serverless-2016-10-31 Resources:   Api:     Type: AWS::Serverless::Api     Properties:       StageName: devtesting       DefinitionBody:         swagger: "2.0"         info:           title:             Ref: AWS::StackName         description: My API that uses custom authorizer         version: 1.0.0         paths:           "/getmesomething":             get:               x-amazon-apigateway-integration:                 httpMethod: GET                 type: aws_proxy         ...
Read more