(aws_cdk.aws_apigatewayv2_integrations.LambdaWebSocketIntegration): produces wrong integration_uri

LambdaWebSocketIntegration (per the example here) seems designed to plug a lambda handler into a WebSocket API Gateway. But it produces the wrong IntegrationUri.

Reproduction Steps

see example here

What did you expect to happen?

Expected a working API Gateway.

What actually happened?

Ended up with a broken API Gateway because the generated IntegrationUri is wrong.

Environment

• CDK CLI Version : 1.94.1 (build 60d8f91)
• Framework Version:
• Node.js Version:
• OS :
• Language (Version):

Other

The IntegrationUri produced is

            "IntegrationUri": "arn:aws:lambda:us-east-2:$$ACCOUNT ID redacted$$:function:sampleContainerFunction",

but a correct one would be

            "IntegrationUri": "arn:aws:apigateway:us-east-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-east-2:$$ACCOUNT ID redacted$$:function:sampleContainerFunction/invocations",

For documentation on this “invocations” format for the IntegrationUri, please see this doc.

The correct AWS CLI command create-integration shows the format:

aws apigatewayv2 create-integration --api-id aabbccddee --integration-type AWS_PROXY --integration-method POST --integration-uri arn:aws:apigateway:us-east-1:lambda:path/2015-03-31/functions/arn:aws:lambda:us-east-1:123412341234:function:simpleproxy-echo-e2e/invocations

---

This is 🐛 Bug Report

[nija-at]

cc @ayush987goyal

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.