# aws-api-gateway Published articles for aws-api-gateway. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## AWS API Gateway's Request Validation: Navigating the Quirks DevFeed: [AWS API Gateway's Request Validation: Navigating the Quirks]() Original publisher: [Read original article]() Author: Thomas Klein Published: 2024-08-09T12:07:11Z Content type: tutorial Language: en Sources: [Homegate Engineering Blog - Medium]() Topics: [Amazon API Gateway](), [Amazon Web Services](), [API](), [gateway](), [JSON Schema](), [TypeScript](), [configuration](), [enum](), [HTTP]() Tags: [api](), [api-gateway](), [aws](), [aws-api-gateway](), [aws-lambda](), [enum](), [gateway](), [handler](), [http](), [json](), [json-schema](), [middleware](), [middy](), [tests](), [type-safety](), [typescript](), [validation](), [zod]() ### AI overview This tutorial examines AWS API Gateway request validation. It explains that query-parameter presence is checked, but enum values may not be enforced, while POST and PUT payloads are validated with JSON Schema Draft 4. It also discusses generic error messages and TypeScript-based validation approaches. ### Source excerpt AWS API Gateway's request validation follows a specific set of rules that developers should be aware of when setting up their APIs. While it offers some validation features, it's important to understand its scope and limitations. Let's examine how it works with a common API configuration: parameters: - name: offerType in: query required: true description: RENT or BUY schema: type: string enum: - RENT - BUY With this configuration, API Gateway diligently checks for the presence of the query parameter, returning an HTTP 400 error if it's missing. However, it falls short when it comes to validating the actual value. Surprisingly, it would accept "KERMIT" without batting an eye, despite the clear enum specification. This behavior, while documented, can be a source of frustration for developers expecting more comprehensive validation. Interestingly, API Gateway shows more validation prowess with POST and PUT requests. It validates request payloads using JSON Schema Draft 4, demonstrating a somewhat inconsistent approach to input validation across different HTTP methods. Even when it does catch an error, API Gateway's feedback is less than illuminating. Instead of specific error details, you're met with a generic {"message": "Invalid request body"}. For more information, you'll need to dig into the associated log streams, which isn't ideal for surfacing error details in API responses. Example output in AWS console from a failed request validation when a body request validator is setup. API Gateway's validation is handy, but it leaves a lot to be desired. Developers often need to add extra checks for a truly robust API. While API Gateway supports various integrations and Lambda languages, let's focus on TypeScript. TypeScript's strong typing and runtime checks can catch issues early, sparing your users from cryptic error messages. Let's explore how to use this to make your API smarter and your users happier. Option 1: DIY Validation (AKA The "I've Got Trust Issues" Approac ## Connecting Block Business Units with AWS API Gateway DevFeed: [Connecting Block Business Units with AWS API Gateway]() Original publisher: [Read original article]() Author: Michael Weissbacher Published: 2023-05-18T13:00:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Amazon API Gateway](), [Amazon Web Services](), [Security](), [SPIFFE](), [SPIRE]() Tags: [api-gateway](), [aws](), [aws-api-gateway](), [engineering](), [network](), [security](), [spiffe](), [spire]() ### AI overview This article explains how Block integrates acquired companies with its internal service mesh using AWS API Gateway as an identity translation layer. The Farcars infrastructure maps acquisition-native identities and IAM-based SigV4 calls to Block-native mutual TLS, enabling isolated and reusable cross-mesh communication. ### Source excerpt Secure cross-mesh communication using in-mesh bastions ## re:Invent 2019 - AWS API Gateway v2 for HTTP DevFeed: [re:Invent 2019 - AWS API Gateway v2 for HTTP]() Original publisher: [Read original article]() Author: Fernando Medina Corey Published: 2019-12-04T00:00:00Z Content type: news Language: en Sources: [Serverless Blog]() Topics: [Amazon API Gateway](), [Amazon Web Services](), [API](), [HTTP]() Tags: [api](), [api-gateway](), [aws](), [aws-api-gateway](), [aws-lambda](), [cloud-computing](), [faas](), [function-as-a-service](), [http](), [infrastructure-as-code](), [news](), [serverless](), [serverless-architecture](), [serverless-framework]() ### AI overview AWS announced support for HTTP APIs in AWS API Gateway v2. ### Source excerpt AWS just announced support for HTTP APIs in AWS API Gateway v2. ## Serverless V1.0 Beta 2 DevFeed: [Serverless V1.0 Beta 2]() Original publisher: [Read original article]() Author: Philipp Müns Published: 2016-08-17T00:00:00Z Content type: release Language: en Sources: [Serverless Blog]() Topics: [serverless framework](), [Cross-origin resource sharing (CORS)](), [Amazon API Gateway](), [Amazon Web Services]() Tags: [2](), [api](), [api-gateway](), [aws](), [aws-api-gateway](), [aws-lambda](), [cloud-computing](), [cors](), [faas](), [function-as-a-service](), [infrastructure-as-code](), [news](), [serverless](), [serverless-architecture](), [serverless-framework](), [v1]() ### AI overview Serverless V1.0 Beta 2 adds CORS support for AWS API Gateway in the serverless framework. ### Source excerpt CORS support added for AWS API Gateway in the serverless framework