REST API gateway cross region VPC link

Your logic makes sense, however based on this: https://docs.aws.amazon.com/apigateway/latest/developerguide/getting-started-with-private-integration.html When you create the VPC Link, you must have the Network Load Balancer created in the same Region as your API for the Network Load Balancer to be present in the list. If you try in your console even if you do the VPC Peering before creating the VPC Link., it is not possible to choose the NLB in the VPC Link configuration. If this helps you please accept the answer.

I have a similar problem, that I cannot find a solution to. I too have a setup where I have an APIGW in us-east-1, targeting an NLB in a private subnet in the same region. I want to have another APIGW in another region, but to target the NLB in us-east-1.

For example: US-EAST-1: REST API call --> (public subnet) APIGW --> (private subnet) NLB --> ALB --> ECS.

US-WEST-1: Rest API call --> (public subnet) APIGW --> (target NLB in us-east-1 and continue the flow in us-east-1)

Or if that is not possible it is also fine to have NLB also in US-WEST-1 and target the ALB in us-east-1. I have setup VPC peering, but I cannot seem to configure the target groups in NLB or ALB for cross region.