学习使用 AWS API Gateway V2 | 隔叶黄莺 Yanbin Blog

2021-12-23 | 阅读(677)

关于 AWS API Gateway V1, 写过一篇笔记 Lambda + API Gateway 创建需 API Key 验证的 API。 AWS 又推出了 API Gateway V2(服务管理/理解层面), 它同样可以用来作 HTTP-PROXY 调用 REST API, WebSocket; AWS-PROXY 调用 Lambda, 还能直接调用 AWS 的其他服务，如 StepFunction, SQS 等。

但是 API Gateway V2 把 V1 中的 API Key 验证功能去掉了，这有点为了赚钱耍无赖了，先前是 API Key 验证不过时不会调用 Lambda, 现在可用 Lambda 来验证 API 调用，也就是不管 API Key 对与不对，都会去调用 Lambda 从而实现从你的帐户上扣钱的功能。

在 V1 中创建整套服务的过程基本是 Resource -> Method -> Integration -> Stage。而在 V2 中的过程是 Integration -> Route -> Stage, 把 Resource 和 Method 合而为一，比如 Route Key 写成 GET /users.

下面照旧以 Terraform 的方式来叙述使用 API Gateway V2 如何实现 HTTP 代理，调用 Lambda, 及使用 AWS 服务(以 SQS 为例)，或与 VPC 内部的服务集成。首先是一个基本的框架，含 API 本身和 Stage

resource "aws_apigatewayv2_api" "example" {
  name          = "test-http-api"
  protocol_type = "HTTP"
}

resource "aws_apigatewayv2_stage" "example" {
  api_id = aws_apigatewayv2_api.example.id
  name   = "stg"
  auto_deploy = true
}

resource "aws_apigatewayv2_api" "example" {

name = "test-http-api"

protocol_type = "HTTP"

}

resource "aws_apigatewayv2_stage" "example" {

api_id = aws_apigatewayv2_api.example.id

name = "stg"

auto_deploy = true

}

执行后回到 AWS 的 Web 控制台看到的就是 API Gateway V2 的界面，AWS 并不会告诉你这是 V2 的界面，但可留意到左边的菜单不一样了，由 V1 的 API/Resources 变成了 Develop/Routes, 其他操作菜单的也都有了变化

Stage 帮我们产生了一个 Invoke URL, 比如 Stage 为 stg, 得到一个类似这样的 URL https://fsoaey6ra4.execute-api.us-east-1.amazonaws.com/stg. 接着就看各种功能的实现

API Gateway V2 与 Lambda 的集成

基本要素与 API Gateway V1 保持一致，外部访问用 GET/POST/PUT 等，但 API Gateway 内部与 Lambda 的通信是用 POST 的，同时要具备相应的权限，因为在 Lambda 方面同样是加上相应的 API Gateway 触发器。

resource "aws_apigatewayv2_integration" "lambda" {
  api_id           = aws_apigatewayv2_api.example.id
  integration_type = "AWS_PROXY"
  integration_method = "POST"
  integration_uri    = aws_lambda_function.example.invoke_arn
  payload_format_version = "2.0"
}

resource "aws_apigatewayv2_route" "lambda" {
  api_id = aws_apigatewayv2_api.example.id
  route_key = "GET /lambda/users/{userId}"
  target = "integrations/${aws_apigatewayv2_integration.lambda.id}"
}

resource "aws_lambda_permission" "allow_api_gateway" {
  action        = "lambda:InvokeFunction"
  function_name = aws_lambda_function.example.function_name
  principal     = "apigateway.amazonaws.com"
  source_arn    = "${aws_apigatewayv2_api.example.execution_arn}/*/GET/lambda/users/{userId}"
}

resource "aws_apigatewayv2_integration" "lambda" {

api_id = aws_apigatewayv2_api.example.id

integration_type = "AWS_PROXY"

integration_method = "POST"

integration_uri = aws_lambda_function.example.invoke_arn

payload_format_version = "2.0"

}

resource "aws_apigatewayv2_route" "lambda" {

api_id = aws_apigatewayv2_api.example.id

route_key = "GET /lambda/users/{userId}"

target = "integrations/${aws_apigatewayv2_integration.lambda.id}"

}

resource "aws_lambda_permission" "allow_api_gateway" {

action = "lambda:InvokeFunction"

function_name = aws_lambda_function.example.function_name

principal = "apigateway.amazonaws.com"

source_arn = "${aws_apigatewayv2_api.example.execution_arn}/*/GET/lambda/users/{userId}"

}

Lambda 资源的创建这里省略了，上面的 route_key 需要更稍加理解，它是 V1 中的 method resource 的合成表示方式，比如 POST /lambda/users 等。甚至还能用 $default, 表示对 Invoke URL 任何形式的请求, 但对于集成 Lambda 的 Gateway, 设置 route_key 为 $default 的话，aws_lambda_permission 中的 source_arn 将变得难以配置。

配置好后，用下面的方式就能调用 Lambda

$ curl https://fsoaey6ra4.execute-api.us-east-1.amazonaws.com/stg/lambda/users/1234

在 Lambda 中可打印出完整的 event, 可帮助我们理解怎么传递，及解析请求数据的。

API Gateway V2 作为 HTTP(S) 代理

我们可完全用 API Gateway V2 作为一个 HTTP(S) 的代理，发往 API Gateway 上的所有请求全部转发到后端 HTTP(S) 服务

resource "aws_apigatewayv2_integration" "http-proxy" {
  api_id           = aws_apigatewayv2_api.example.id
  integration_type = "HTTP_PROXY"

  integration_method = "ANY"
  integration_uri    = "http://example.com/{proxy}"
}

resource "aws_apigatewayv2_route" "http-proxy" {
  api_id    = aws_apigatewayv2_api.example.id
  route_key = "ANY /go/{proxy+}"
  target = "integrations/${aws_apigatewayv2_integration.http-proxy.id}"
}

resource "aws_apigatewayv2_integration" "http-proxy" {

api_id = aws_apigatewayv2_api.example.id

integration_type = "HTTP_PROXY"

integration_method = "ANY"

integration_uri = "http://example.com/{proxy}"

}

resource "aws_apigatewayv2_route" "http-proxy" {

api_id = aws_apigatewayv2_api.example.id

route_key = "ANY /go/{proxy+}"

target = "integrations/${aws_apigatewayv2_integration.http-proxy.id}"

}

上面 integration_type 和 route_key 中的 method 都是 ANY, 并且由 ANY /go/{proxy+} 到 ANY http://example.com/{proxy} 产生的效果就是

GET https://fsoaey6ra4.execute-api.us-east-1.amazonaws.com/stg/go/ -> GET http://examle.com/
POST https://fsoaey6ra4.execute-api.us-east-1.amazonaws.com/stg/go/aaa/bbb -> POST http://example.com/aaa/bbb
......

也可以显式的逐个指定 route_key, 如下面那样随意发挥

route_key = "GET /abc", integration_method="POST", integration_url = "http://example.com/xyz/kk"

但是必须清楚一点，API Gateway 的 HTTP_PROXY 只能直接与 public 的 HTTP(S) 集成，也就是你在 VPC 内部创建了的 EC2 或 ECS 启动的 HTTP(S) 服务不能直接访问，必须外加一个 ELB 和 VPC Link 才能与 API Gateway 连接起来，后面会讲到。

API Gateway V2 与 AWS 服务的集成(以 SQS 为例)

API Gateway V2 除了调用 Lambda 外，还能调用 AWS 的其他服务，下面以 SQS-SendMessage 为例

resource "aws_apigatewayv2_integration" "sqs" {
  api_id              = aws_apigatewayv2_api.example.id
  credentials_arn     = "<IAM role arn here>"
  integration_type    = "AWS_PROXY"
  integration_subtype = "SQS-SendMessage"

  request_parameters = {
    "QueueUrl"    = "$request.header.queueUrl"
    "MessageBody" = "$request.body.message"
  }
}

resource "aws_apigatewayv2_route" "sqs" {
  api_id    = aws_apigatewayv2_api.example.id
  route_key = "POST /sqs"
  target = "integrations/${aws_apigatewayv2_integration.sqs.id}"
}

resource "aws_apigatewayv2_integration" "sqs" {

api_id = aws_apigatewayv2_api.example.id

credentials_arn = "<IAM role arn here>"

integration_type = "AWS_PROXY"

integration_subtype = "SQS-SendMessage"

request_parameters = {

"QueueUrl" = "$request.header.queueUrl"

"MessageBody" = "$request.body.message"

}

resource "aws_apigatewayv2_route" "sqs" {

api_id = aws_apigatewayv2_api.example.id

route_key = "POST /sqs"

target = "integrations/${aws_apigatewayv2_integration.sqs.id}"

}

如果 IAM role 的权限没问题的话，下面的请求将能发送一条 SQS 消息到队列中

$ curl -X POST -H "queueUrl:https://sqs.us-east-1.amazonaws.com/123456789088/test-queue" \
-H "content-type:application/json" \
https://fsoaey6ra4.execute-api.us-east-1.amazonaws.com/stg/sqs \
--data '{"message": "your message body here"}'

当 integration_type 为 AWS_PROXY 时，integration_subtype 要以选择以下其中一个：

EventBridge-PutEvents
SQS-SendMessage
SQS-ReceiveMessage
SQS-DeleteMessage
SQS-PurgeQueue
AppConfig-GetConfiguration
Kinesis-PutRecord
StepFunctions-StartExecution
StepFunctions-StartSyncExecution
StepFunctions-StopExecution

详情见 Integration subtype reference

关于 request_parameters，response_parameters 的映射可参考 Transforming API requests and responses

另外，如果在调用 API Gateway 时出现无法理解的错误时，请启用 API Gateway 的 Logging, 并在 Log format 中按相同规则添加以下三个字段

$context.integrationErrorMessage
$context.error.message
$context.error.responseType

更多 API Gateway 日志相关的字段，请见 Customizing HTTP API access logs

API Gateway V2 连接 Private ELB

这样做的好处估计是用 Private ELB 提供多数的服务内部使用，其中少数 API 需要暴露给外部，所以就以 API Gateway 作为桥梁。为此，首先需创建一个 VPC Link, 自然就要提供相应的 Security Group, Subnet，以及需要被连接的 Private ELB 的监听器的 ARN

resource "aws_apigatewayv2_vpc_link" "private" {
  name               = "private_api"
  security_group_ids = ["sg-111e222g"]
  subnet_ids         = ["subnet-1122aa8f", "subnet-aa123e86"]
}

resource "aws_apigatewayv2_integration" "vpc" {
  api_id           = aws_apigatewayv2_api.example.id
  credentials_arn  = "<IAM role ARN here>"
  integration_type = "HTTP_PROXY"
  integration_uri  = "<Your ELB Listener ARN here>"

  integration_method = "ANY"
  connection_type    = "VPC_LINK"
  connection_id      = aws_apigatewayv2_vpc_link.private.id
}

resource "aws_apigatewayv2_route" "vpc" {
  api_id    = aws_apigatewayv2_api.example.id
  route_key = "ANY /{proxy+}"
  target = "integrations/${aws_apigatewayv2_integration.vpc.id}"
}

resource "aws_apigatewayv2_vpc_link" "private" {

name = "private_api"

security_group_ids = ["sg-111e222g"]

subnet_ids = ["subnet-1122aa8f", "subnet-aa123e86"]

}

resource "aws_apigatewayv2_integration" "vpc" {

api_id = aws_apigatewayv2_api.example.id

credentials_arn = "<IAM role ARN here>"

integration_type = "HTTP_PROXY"

integration_uri = "<Your ELB Listener ARN here>"

integration_method = "ANY"

connection_type = "VPC_LINK"

connection_id = aws_apigatewayv2_vpc_link.private.id

}

resource "aws_apigatewayv2_route" "vpc" {

api_id = aws_apigatewayv2_api.example.id

route_key = "ANY /{proxy+}"

target = "integrations/${aws_apigatewayv2_integration.vpc.id}"

}

与前面的 HTTP_PROXY 大致类似，不同的就是 connection_type 为 VPC_LINK。完后，访问 Invoke URL 的所有类型的请求悉数转发到了 ELB 监听器上了。

API Gateway 使用 VPC_LINK 就能打通与 VPC 内部的服务，在网络通路上把请求代理到 EC2 机器上是没问题的，或可借助于 Route 53 解析到某个 Private 的 EC2 上，但它没提供这样的功能，因为跳过 ELB 的话估计会少赚些钱。

总结

配置 API Gateway 时很容易碰到各种问题，比使用 ELB + ECS 碰到的问题会多得多，因为 API Gateway 与后端服务之间对我们来说是个黑盒子。

API Gateway V2 配置的重点在 aws_apigatewayv2_integration, 还有许多参数前面尚未提及，如代理时的 passthrough_behavior. payload_format_version 2.0 比 1.0 更宽松，Lambda 中返回的字符串自动封装。还有 response_parameters 等等。

API Gateway V2 与 V1 相比而言就只觉得写 route_key 比单独的定义每一个 Resource, Method 要简单，其实质好像没有什么变化。所以在 AWS Web 控制台并不标识出是 V2 还是 V1 大概也就是这个原因, 因为对于用户而言还真就是控制台 UI 的变化而已。

其他的， API Gateway V2 集成 WebSocket 或许还有些新的内容，实际工作中还未真正用过 WebSocket，故未作深究。

[2022-01-10]：API Gateway V1 和 V2 的 Lambda 请求 event 数据格式是不一样的，以下分别是 V1 和 V2 的 event

API Gateway V1 Lambda event:

{
    "resource": "/version",
    "path": "/version",
    "httpMethod": "GET",
    "headers": {
        "Accept": "*/*",
        "Accept-Encoding": "gzip, deflate, br",
        "Cache-Control": "no-cache",
        "CloudFront-Forwarded-Proto": "https",
        "CloudFront-Is-Desktop-Viewer": "true",
        "CloudFront-Is-Mobile-Viewer": "false",
        "CloudFront-Is-SmartTV-Viewer": "false",
        "CloudFront-Is-Tablet-Viewer": "false",
        "CloudFront-Viewer-Country": "US",
        "Host": "2ek2gezgwa.execute-api.us-east-1.amazonaws.com",
        "Postman-Token": "eba2a85c-e1a0-4fed-96de-e7cbef7bfa50",
        "User-Agent": "PostmanRuntime/7.28.4",
        "Via": "1.1 6232ab8d1c60778053fd7b2d4bbeb7e4.cloudfront.net (CloudFront)",
        "X-Amz-Cf-Id": "xHpEidy5FPriZAD_uYzpR-BOgtD1zduLHBIfrUWzG5VfFiMv4T8L0w==",
        "X-Amzn-Trace-Id": "Root=1-61dcd392-714872c96460463307ba18f1",
        "x-api-key": "2343252ZE9",
        "X-Forwarded-For": "206.220.18.42, 64.252.169.166",
        "X-Forwarded-Port": "443",
        "X-Forwarded-Proto": "https"
    },
    "multiValueHeaders": {
        "Accept": [
            "*/*"
        ],
        "Accept-Encoding": [
            "gzip, deflate, br"
        ],
        "Cache-Control": [
            "no-cache"
        ],
        "CloudFront-Forwarded-Proto": [
            "https"
        ],
        "CloudFront-Is-Desktop-Viewer": [
            "true"
        ],
        "CloudFront-Is-Mobile-Viewer": [
            "false"
        ],
        "CloudFront-Is-SmartTV-Viewer": [
            "false"
        ],
        "CloudFront-Is-Tablet-Viewer": [
            "false"
        ],
        "CloudFront-Viewer-Country": [
            "US"
        ],
        "Host": [
            "2ek2gezgwa.execute-api.us-east-1.amazonaws.com"
        ],
        "Postman-Token": [
            "eba2a85c-e1a0-4fed-96de-e7cbef7bfa50"
        ],
        "User-Agent": [
            "PostmanRuntime/7.28.4"
        ],
        "Via": [
            "1.1 6232ab8d1c60778053fd7b2d4bbeb7e4.cloudfront.net (CloudFront)"
        ],
        "X-Amz-Cf-Id": [
            "xHpEidy5FPriZAD_uYzpR-BOgtD1zduLHBIfrUWzG5VfFiMv4T8L0w=="
        ],
        "X-Amzn-Trace-Id": [
            "Root=1-61dcd392-714872c96460463307ba18f1"
        ],
        "x-api-key": [
            "pmjb339byoPdgfiSmMR6aUmSsO6QPPX2gHJOKZE9"
        ],
        "X-Forwarded-For": [
            "206.220.18.42, 64.252.169.166"
        ],
        "X-Forwarded-Port": [
            "443"
        ],
        "X-Forwarded-Proto": [
            "https"
        ]
    },
    "queryStringParameters": {
        "debug": ""
    },
    "multiValueQueryStringParameters": {
        "debug": [
            ""
        ]
    },
    "pathParameters": null,
    "stageVariables": null,
    "requestContext": {
        "resourceId": "rovr9k",
        "resourcePath": "/version",
        "httpMethod": "GET",
        "extendedRequestId": "LwX-5E7yoAMFpJg=",
        "requestTime": "11/Jan/2022:00:47:14 +0000",
        "path": "/qa/version",
        "accountId": "913903414417",
        "protocol": "HTTP/1.1",
        "stage": "qa",
        "domainPrefix": "2ek2gezgwa",
        "requestTimeEpoch": 1641862034361,
        "requestId": "ab3d1839-d4a7-4e8c-8b43-270e426c6875",
        "identity": {
            "cognitoIdentityPoolId": null,
            "cognitoIdentityId": null,
            "apiKey": "2343252ZE9",
            "principalOrgId": null,
            "cognitoAuthenticationType": null,
            "userArn": null,
            "apiKeyId": "64rntwaq2h",
            "userAgent": "PostmanRuntime/7.28.4",
            "accountId": null,
            "caller": null,
            "sourceIp": "206.220.18.42",
            "accessKey": null,
            "cognitoAuthenticationProvider": null,
            "user": null
        },
        "domainName": "2ek2gezgwa.execute-api.us-east-1.amazonaws.com",
        "apiId": "2ek2gezgwa"
    },
    "body": null,
    "isBase64Encoded": false
}

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

{

"resource": "/version",

"path": "/version",

"httpMethod": "GET",

"headers": {

"Accept": "*/*",

"Accept-Encoding": "gzip, deflate, br",

"Cache-Control": "no-cache",

"CloudFront-Forwarded-Proto": "https",

"CloudFront-Is-Desktop-Viewer": "true",

"CloudFront-Is-Mobile-Viewer": "false",

"CloudFront-Is-SmartTV-Viewer": "false",

"CloudFront-Is-Tablet-Viewer": "false",

"CloudFront-Viewer-Country": "US",

"Host": "2ek2gezgwa.execute-api.us-east-1.amazonaws.com",

"Postman-Token": "eba2a85c-e1a0-4fed-96de-e7cbef7bfa50",

"User-Agent": "PostmanRuntime/7.28.4",

"Via": "1.1 6232ab8d1c60778053fd7b2d4bbeb7e4.cloudfront.net (CloudFront)",

"X-Amz-Cf-Id": "xHpEidy5FPriZAD_uYzpR-BOgtD1zduLHBIfrUWzG5VfFiMv4T8L0w==",

"X-Amzn-Trace-Id": "Root=1-61dcd392-714872c96460463307ba18f1",

"x-api-key": "2343252ZE9",

"X-Forwarded-For": "206.220.18.42, 64.252.169.166",

"X-Forwarded-Port": "443",

"X-Forwarded-Proto": "https"

"multiValueHeaders": {

"Accept": [

"*/*"

"Accept-Encoding": [

"gzip, deflate, br"

"Cache-Control": [

"no-cache"

"CloudFront-Forwarded-Proto": [

"https"

"CloudFront-Is-Desktop-Viewer": [

"true"

"CloudFront-Is-Mobile-Viewer": [

"false"

"CloudFront-Is-SmartTV-Viewer": [

"false"

"CloudFront-Is-Tablet-Viewer": [

"false"

"CloudFront-Viewer-Country": [

"US"

"Host": [

"2ek2gezgwa.execute-api.us-east-1.amazonaws.com"

"Postman-Token": [

"eba2a85c-e1a0-4fed-96de-e7cbef7bfa50"

"User-Agent": [

"PostmanRuntime/7.28.4"

"Via": [

"1.1 6232ab8d1c60778053fd7b2d4bbeb7e4.cloudfront.net (CloudFront)"

"X-Amz-Cf-Id": [

"xHpEidy5FPriZAD_uYzpR-BOgtD1zduLHBIfrUWzG5VfFiMv4T8L0w=="

"X-Amzn-Trace-Id": [

"Root=1-61dcd392-714872c96460463307ba18f1"

"x-api-key": [

"pmjb339byoPdgfiSmMR6aUmSsO6QPPX2gHJOKZE9"

"X-Forwarded-For": [

"206.220.18.42, 64.252.169.166"

"X-Forwarded-Port": [

"443"

"X-Forwarded-Proto": [

"https"

]

"queryStringParameters": {

"debug": ""

"multiValueQueryStringParameters": {

"debug": [

]

"pathParameters": null,

"stageVariables": null,

"requestContext": {

"resourceId": "rovr9k",

"resourcePath": "/version",

"httpMethod": "GET",

"extendedRequestId": "LwX-5E7yoAMFpJg=",

"requestTime": "11/Jan/2022:00:47:14 +0000",

"path": "/qa/version",

"accountId": "913903414417",

"protocol": "HTTP/1.1",

"stage": "qa",

"domainPrefix": "2ek2gezgwa",

"requestTimeEpoch": 1641862034361,

"requestId": "ab3d1839-d4a7-4e8c-8b43-270e426c6875",

"identity": {

"cognitoIdentityPoolId": null,

"cognitoIdentityId": null,

"apiKey": "2343252ZE9",

"principalOrgId": null,

"cognitoAuthenticationType": null,

"userArn": null,

"apiKeyId": "64rntwaq2h",

"userAgent": "PostmanRuntime/7.28.4",

"accountId": null,

"caller": null,

"sourceIp": "206.220.18.42",

"accessKey": null,

"cognitoAuthenticationProvider": null,

"user": null

"domainName": "2ek2gezgwa.execute-api.us-east-1.amazonaws.com",

"apiId": "2ek2gezgwa"

"body": null,

"isBase64Encoded": false

}

API Gateway V2 Lambda event

{
    "version": "2.0",
    "routeKey": "GET /version",
    "rawPath": "/stg/version",
    "rawQueryString": "debug",
    "headers": {
        "accept": "application/json",
        "accept-encoding": "gzip, deflate, br",
        "cache-control": "no-cache",
        "content-length": "0",
        "content-type": "application/json",
        "host": "uz6f6zn2h3.execute-api.us-east-1.amazonaws.com",
        "postman-token": "fdab8cbf-00ec-43c4-81e7-ffe64fe395ba",
        "user-agent": "PostmanRuntime/7.28.4",
        "x-amzn-trace-id": "Root=1-61dcd659-16a484e4706350e007c7bbb6",
        "x-forwarded-for": "67.175.2.251",
        "x-forwarded-port": "443",
        "x-forwarded-proto": "https"
    },
    "queryStringParameters": {
        "debug": ""
    },
    "requestContext": {
        "accountId": "913903414417",
        "apiId": "uz6f6zn2h3",
        "domainName": "uz6f6zn2h3.execute-api.us-east-1.amazonaws.com",
        "domainPrefix": "uz6f6zn2h3",
        "http": {
            "method": "GET",
            "path": "/stg/version",
            "protocol": "HTTP/1.1",
            "sourceIp": "67.175.2.251",
            "userAgent": "PostmanRuntime/7.28.4"
        },
        "requestId": "LwZt8hFbIAMEMWw=",
        "routeKey": "GET /version",
        "stage": "stg",
        "time": "11/Jan/2022:00:59:05 +0000",
        "timeEpoch": 1641862745096
    },
    "isBase64Encoded": false
}

{

"version": "2.0",

"routeKey": "GET /version",

"rawPath": "/stg/version",

"rawQueryString": "debug",

"headers": {

"accept": "application/json",

"accept-encoding": "gzip, deflate, br",

"cache-control": "no-cache",

"content-length": "0",

"content-type": "application/json",

"host": "uz6f6zn2h3.execute-api.us-east-1.amazonaws.com",

"postman-token": "fdab8cbf-00ec-43c4-81e7-ffe64fe395ba",

"user-agent": "PostmanRuntime/7.28.4",

"x-amzn-trace-id": "Root=1-61dcd659-16a484e4706350e007c7bbb6",

"x-forwarded-for": "67.175.2.251",

"x-forwarded-port": "443",

"x-forwarded-proto": "https"

"queryStringParameters": {

"debug": ""

"requestContext": {

"accountId": "913903414417",

"apiId": "uz6f6zn2h3",

"domainName": "uz6f6zn2h3.execute-api.us-east-1.amazonaws.com",

"domainPrefix": "uz6f6zn2h3",

"http": {

"method": "GET",

"path": "/stg/version",

"protocol": "HTTP/1.1",

"sourceIp": "67.175.2.251",

"userAgent": "PostmanRuntime/7.28.4"

"requestId": "LwZt8hFbIAMEMWw=",

"routeKey": "GET /version",

"stage": "stg",

"time": "11/Jan/2022:00:59:05 +0000",

"timeEpoch": 1641862745096

"isBase64Encoded": false

}

Lambda 在处理 Event 时要注意，关于 Key 的大小写，可以把 event 转换为 CaseInsensitiveDict 来保持兼容

from requests.structures import CaseInsensitiveDict
event = CaseInsensitiveDict(originalEvent)

1 2	from requests.structures import CaseInsensitiveDict event = CaseInsensitiveDict(originalEvent)

确定请求资源也不一样，V1 中取 httpMethod 和 resource 组合，V2 中要取 routeKey。

本文链接 https://yanbin.blog/study-aws-apigateway-v2/, 来自隔叶黄莺 Yanbin Blog

本文采用署名-非商业性使用-相同方式共享 4.0 国际 (CC BY-NC-SA 4.0) 进行许可。

seetimee on 体验 Python FastAPI 的并发能力及线, 进程模型感谢
Yanbin on Mockito 3.4.0 开始可 Mock 静态方法有一个补救，新写了一篇 https://yanbin.blog/mockito-mock-static-method-in-multiple...
Yanbin on 升级到 Spring Boot 3 后 javax.inject.Named 不可用怎么，被抄袭了！算是被机器翻译引用的？
oleksi on 升级到 Spring Boot 3 后 javax.inject.Named 不可用https://www.springcloud.io/post/2023-02/springboot-3-javax-inject-name...
Zhe on 体验 Python FastAPI 的并发能力及线, 进程模型你在trio下得用 trio.sleep()，调用asyncio.sleep() 就会报错。