使用AWS WebSockets API网关的Lambda授权器功能在AWS控制台中产生错误
我们已经通过AWS网关创建了一个连接到lambda函数的WebSocket API，但是为了授权连接/API-Request，我们需要创建一个在Lambda函数之前命中的lambda授权器。目前，这是AWS通过Gateway Websocket Connection授权请求的唯一选项。连接lambda授权器很简单，但是由于某种原因，AWS控制台报告的错误是没有任何意义的，因为授权者已将其附加到$ $ CONENK Route>
授权者具有所有必要的权限。我试图进行简单的理智测试并记录正在通过的事件，但是Lambda授权者被完全忽略了。除了Lambda授权者外，Websocket API和Lambda功能也没有任何问题。到达Lambda授权者似乎只是一个问题。
如果您知道为什么会发生这种情况，请让我知道我们在做什么错。
We've created a Websocket API through AWS Gateway that connects to a Lambda function, but in order to authorize the connection/API-request we need to create a lambda authorizer that is hit before the Lambda function. For now, this is the only option that AWS gives to authorize requests via gateway websocket connection. Hooking up the lambda authorizer is simple, but for some reason the AWS console is reporting an error that doesn't make any sense since the authorizer is attached to the $connect route
The authorizer has all the necessary permissions. I tried to conduct a simple sanity test and log the event that was being passed in, but the lambda authorizer is being completely ignored. Aside from the Lambda authorizer, the websocket API and Lambda function work together without any issues. There just seems to be a problem reaching the lambda authorizer.
If you have any idea why this is is happening, please let me know what we're doing wrong.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论