kayx23 opened a new issue, #11176: URL: https://github.com/apache/apisix/issues/11176
### Description Currently the `aws-lambda` plugin returns `400 Bad Request` for wrong IAM credentials (wrong access key or secret key). The error log is the following and it is not very informative: ```text 2024/04/22 02:10:01 [warn] 277#277: *11342 [lua] plugin.lua:1160: run_plugin(): aws-lambda exits with http status code 400, client: 172.25.0.1, server: _, request: "GET / HTTP/1.1", host: "127.0.0.1:9080" ``` As an enhancement, APISIX could return more telling error message to help users troubleshooting. For example, with AWS CLI `aws sts get-caller-identity`, wrong secret key would lead to the following error msg: ``` An error occurred (SignatureDoesNotMatch) when calling the GetCallerIdentity operation: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. ``` Wrong access key would lead to the following error msg: ``` An error occurred (InvalidClientTokenId) when calling the GetCallerIdentity operation: The security token included in the request is invalid. ``` ### Environment APISIX version (run `apisix version`): 3.9.0 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
