Where is Amazon.CDK.AWS.Apigatewayv2.Alpha WebSocket AWS integration type?

[JobaDiniz]

UPDATE to better explain what I'm trying to accomplish

This is my CDK code:

var api = new WebSocketApi(this, $"{nameof(BrokerRobotStack)}Api", new WebSocketApiProps
{
    RouteSelectionExpression = "$request.body.action",
    DefaultRouteOptions = new WebSocketRouteOptions 
    { 
        Integration = //TODO: which class to instantiate here to create => IntegrationType: AWS
    }
});

Which class do I instantiate in the Integration property of WebSocketRouteOptions to create a AWS IntegrationType? Look at the documentation

AWS: for integrating the route or method request with an AWS service action, [...]. With any other AWS service action, this is known as AWS integration. Supported only for WebSocket APIs.

Like the following CloudFormation yaml:

ApiAuthenticateRouteIntegration:
    Type: AWS::ApiGatewayV2::Integration
    Properties:
      ApiId: !Ref BrokerRobotSocketApi
      IntegrationType: AWS
      IntegrationMethod: POST
      IntegrationUri: !Sub "arn:aws:apigateway:${AWS::Region}:states:action/StartExecution"
     ...

[peterwoodworth]

@github-actions proposed answer You need to install alpha modules separately, see the docs here for more info. Note that there are multiple alpha modules for ApiGatewayV2, so you can find WebSocketLambdaIntegration in the ApiGatewayV2Integrations module.

As for converting CloudFormation to CDK, if you want to do that explicitly you can drop to the L1 Cfn resources found here, since our L1 resources are identical to the CloudFormation ones. Or depending on your exact requirements, you could also use the cloudformation-include module.

[peterwoodworth]

I'm not sure I understand your exact requirements, or what code you already have in place and where exactly you're getting stuck. Could you please go into some more detail regarding these things?

[JobaDiniz]

this is my CDK code:

var api = new WebSocketApi(this, $"{nameof(BrokerRobotStack)}Api", new WebSocketApiProps
{
    RouteSelectionExpression = "$request.body.action",
    DefaultRouteOptions = new WebSocketRouteOptions 
    { 
        Integration = //TODO: which class to instantiate here to create => IntegrationType: AWS
    }
});

Which class do I instantiate in the Integration property of WebSocketRouteOptions to create a AWS IntegrationType? Look at the documentation

AWS: for integrating the route or method request with an AWS service action, [...]. With any other AWS service action, this is known as AWS integration. Supported only for WebSocket APIs.

Like the following CloudFormation yaml:

ApiAuthenticateRouteIntegration:
    Type: AWS::ApiGatewayV2::Integration
    Properties:
      ApiId: !Ref BrokerRobotSocketApi
      IntegrationType: AWS
      IntegrationMethod: POST
      IntegrationUri: !Sub "arn:aws:apigateway:${AWS::Region}:states:action/StartExecution"
     ...

[peterwoodworth]

We don't have a proper solution for specifying this @JobaDiniz, I created a feature request for us to track adding L2 support for this. However, you can work around it with escape hatches. You can see the examples of how to do this in dotnet, but here's the construct path you can take as an example in TypeScript

    const api = new apigwv2.WebSocketApi(this, 'Api', {
      defaultRouteOptions: {
        integration: new apiintegrations.WebSocketLambdaIntegration('fn', new lambda.Function(this, 'Fn', {
          code: lambda.Code.fromInline('console.log("hello world")'),
          handler: 'index.handler',
          runtime: lambda.Runtime.NODEJS_18_X,
        })),
      }
    });

    (api.node.findChild('$default-Route').node.findChild('fn').node.defaultChild as apigwv2cfn.CfnIntegration).addPropertyOverride('IntegrationType', 'AWS')

If you're supplying the default route, you'll want to find the $default-Route child, this won't ever change. Then, on that you'll want to find the child with the same name that you provide in the id prop of WebSocketLambdaIntegration. Here, mine is fn. From there you can access the default child as a CfnIntegration, then modify its IntegrationType to be AWS with the addPropertyOverride method.

[peterwoodworth]

@JobaDiniz There is not going to be any easy way to implement this with L2s. Please create a feature request for the high level pattern you would like to see supported. For now, I would recommend using the L1 constructs that directly translate to CloudFormation resources

[peterwoodworth]

For clarity, we'll need a new construct in @aws-cdk/aws-apigatewayv2-integrations-alpha to see this supported