- 최신
- 최다 투표
- 가장 많은 댓글
You're correct. API Gateway's request parameter mapping at the integration level is indeed limited to a global scope for all routes within an API. While there's no direct way to achieve route-specific parameter mapping at the API Gateway level, here are some potential workarounds:
1/ Lambda Function Logic -- > Leverage Path Parameters: If you have control over the route paths, you can use path parameters to differentiate requests.
Example: /route1/{tableName} and /route2/{tableName} .In your Lambda function, extract the tableName from the path parameters and use it accordingly.
2/ Use API Gateway Method Request: While not ideal for large-scale scenarios, you can manually add query string parameters to the method request for each route. This approach can be tedious for multiple routes.
Hope it helps.