feat(apigatewayv2): WebSocket API - IAM authorizer support#21393
feat(apigatewayv2): WebSocket API - IAM authorizer support#21393mergify[bot] merged 10 commits intoaws:mainfrom
Conversation
|
|
…k into add-websocket-iam-authorizer
52bdb92 to
ad97176
Compare
a4339ca to
712562c
Compare
comcalvi
left a comment
There was a problem hiding this comment.
I don't understand what functionality this adds. From our existing docs (the readme), it looks like this is already supported.
bcc5c5f to
64e1598
Compare
64e1598 to
dbc63f5
Compare
Thanks for the review. I should have provided more context, I've now updated the description as well |
corymhall
left a comment
There was a problem hiding this comment.
Just a minor comment on the readme and then I'm good with this
…k into add-websocket-iam-authorizer
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
This adds support for
AWS_IAMas Authorizer for Websocket $connect route.The CDK supports adding IAM Authorizer as
authorizationTypeforHttpApi, but does not support it forWebSocketApiL2 constructIAM Authorization is covered in the docs here.
It works the same way as REST or HTTP API's where you can make an endpoint (connect route for websocket) publicly inaccessible, and setup an IAM user, and allow access using signed URL's
The above doc links back to this section which explains the
AWS_IAMThis is also available from the AWS console for Websocket connect Route:
Adding new Unconventional Dependencies:
New Features
yarn integto deploy the infrastructure and generate the snapshot (i.e.yarn integwithout--dry-run)?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license