Issue with HTTP API Autodeployment - VPC link error

Question

I had not updated my HTTP API Gateway in some time. I tried to make a change today to my dev stage which uses autodeployment, and I see this message: 
Deployment attempt failed: Vpc link bwk5ve was not found in account

The thing is, I do not remember ever creating a VPC link. The server the API Gateway forwards requests to has a public IP address. There are no NAT gateways, load balancers, etc. The API Gateway is functioning normally.

The list of VPC links is empty - so there appears to be a 'ghost' reference to a VPC link and now I cannot autodeploy any changes.

How can I fix this please?

oldtimehacker · Answer

I fixed it. I believe I had previously created some infra for another stage, then deleted it. But even though those stages were gone, an old integration referenced a deleted VPC link.

The way to solve this is to look carefully at your API Gateway's configuration and so you can search for things more easily, and this is most easily accomplished with the command:
`aws apigatewayv2 export-api`

Once I deleted the offending integration I was successful.

Riku_Kobayashi · Answer

Hello.

Can I check VPC links with the AWS CLI "get-vpc-links" command?  
https://awscli.amazonaws.com/v2/documentation/api/latest/reference/apigateway/get-vpc-links.html

Also, is it possible that a VPC link was mistakenly created during the previous deployment or manually created through the management console, causing discrepancies with the automatic deployment?

Issue with HTTP API Autodeployment - VPC link error

Relevant content