aws-samples / simple-websockets-chat-app

This SAM application provides the Lambda functions, DynamoDB table, and roles to allow you to build a simple chat application based on API Gateway's new WebSocket-based API feature.
MIT No Attribution
682 stars 280 forks source link

APIGateway trigger not showing in Lambda console #15

Closed alexandrecanuto closed 5 years ago

alexandrecanuto commented 5 years ago

When I built this sample, the API Gateway trigger integration shows up in Lambda console: Captura de Tela 2019-03-08 às 19 04 26

When building my own app, everything works just fine, but the trigger does not show up in Lambda console: Captura de Tela 2019-03-08 às 19 04 05

Again, I should point out that my API is working just fine, it's just odd and makes me feel like I might be missing something important.

My template looks pretty much the same (so does the API Gateway route overview in the console):

...

ConnectRoute:
    Type: AWS::ApiGatewayV2::Route
    Properties:
      ApiId: !Ref RedeChatWSApi
      RouteKey: $connect
      AuthorizationType: NONE
      OperationName: ConnectRoute
      Target: !Join
        - "/"
        - - "integrations"
          - !Ref ConnectInteg
  ConnectInteg:
    Type: AWS::ApiGatewayV2::Integration
    Properties:
      ApiId: !Ref RedeChatWSApi
      Description: Connect integration.
      IntegrationType: AWS_PROXY
      IntegrationUri:
        Fn::Sub:
          arn:aws:apigateway:${AWS::Region}:lambda:path/2015-03-31/functions/${OnConnectFunction.Arn}/invocations

...

Outputs:
  OnConnectFunctionArn:
    Description: OnConnect function ARN.
    Value: !GetAtt OnConnectFunction.Arn

Thanks for the help. 😀

dgomesbr commented 5 years ago

I'm taking a look on this one.

dgomesbr commented 5 years ago

@alexandrecanuto can you post your template.yml file? I can't reproduce this one.

dgomesbr commented 5 years ago

can't reproduce

amoffat commented 2 years ago

Old issue, but I ran into a similar problem which I answered here https://superuser.com/questions/1695597/aws-lambda-not-showing-apigateway-trigger-in-console-ui-but-it-works