Invalid VpcLink id 8gdno9 referenced in integration

0

I created a VPC Link and can see the ID, yet when I try to connect a websocket route after setting it as a stage variable i get the error "Invalid VpcLink id 8gdno9 referenced in integration". What other ID should I be passing?

Enter image description here

If I do aws apigatewayv2 get-vpc-link --vpc-link-id 8gdno9 --profile sw --region us-east-1 I get

{ "CreatedDate": "2024-03-14T17:40:55+00:00", "Name": "N Virgina default", "SecurityGroupIds": [ "sg-093c1dd279bcefbc0" ], "SubnetIds": [ "subnet-0c6615fa0e7baf17a", "subnet-023c95cf1d67ae5bf", "subnet-0929c58fae3a0eb3e", "subnet-0c6fde6a37cf00331", "subnet-0f85eabd647061309" ], "Tags": {}, "VpcLinkId": "8gdno9", "VpcLinkStatus": "AVAILABLE", "VpcLinkStatusMessage": "VPC link is ready to route traffic", "VpcLinkVersion": "V2" }

This sure seems like a bug.

已提问 2 个月前144 查看次数
2 回答
0

"VpcLinkVersion": "V2"

This indicates that the VPC Link is for HTTP API's. For use with Websockets and RestAPI, you need to create VPCLink for RestAPI

Ref: https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-private-integration.html

profile pictureAWS
支持工程师
Bony_T
已回答 1 个月前
0
  1. Verify VPC link is in AVAILABLE state; recreate if in FAILED state.
  2. Confirm VPC link endpoint connection is AVAILABLE.
  3. For WebSocket APIs, manually add connectionId as header on integration request.
  4. Ensure VPC link load balancer is configured on correct port; check network ACLs and security groups.
  5. Verify backend service allows inbound traffic and security groups are configured correctly.
  6. Examine integration logs for further details on failure, such as invalid configurations or network accessibility issues. https://repost.aws/knowledge-center/api-gateway-vpc-link-integration
profile picture
专家
已回答 1 个月前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则

相关内容