AWS API Gateway access private API Gateway in another account

Question

Is it possible to have a (public) AWS API Gateway in account A access a private API Gateway sitting in account B?

If so, how is this configured?

This article describes the setup, but uses a VPC within account A with an NLB and VPC peering.

Are there any other alternatives?

Answer 1

Apart from the VPC peering approach, you can implement your use case using Lambda functions (placed in a VPC in account A) and the private API in account B allowing the VPC in account A access in its resource policy. Also note, the two VPCs should be in the same region for this setup.

How it would look:

• Public API in account A has integration set up with a Lambda function in the same account

• Lambda function is placed inside a VPC (let's call this VPC A)

• Private API in account B allows VPC A access in its resource policy

• Lambda function in account A should now be able to invoke the private API and return the required data