How can I access an API Gateway private REST API in another account using an interface VPC endpoint?

preview_player
Показать описание

Ruiling shows you how to access an API Gateway private REST API in another account using an interface VPC endpoint.
Рекомендации по теме
Комментарии
Автор

can we access private api from the different account when the vpc in another account is connected with the transit gateway?

aravind
Автор

Can we use vpc id only or do we really need to create an interface endpoint?

janaubreytampos
Автор

Thanks. Very well, helpe me a Lot..rsrs I'd like to known more about a API Gateway using VPCLink and the others. Thanks. Best Regards from Brazil, Rio Janeiro.

aluanan
Автор

I'm having a problem testing a Rest API from a subnet without internet access.

franciscojaviervasquezhern
Автор

In this video, the presenter used VPC interface endpoints for accessing private APIs. This is one way of doing it.
Alternatively, we can also use VPC Endpoint Services (with AWS PrivateLink) to achieve the same outcome.
The account where you are deploying the private API needs an NLB in front of it for the VPC Endpoint service to work.

Web.
Автор

Does API Gateway (Account: A, Region: east-us-1) access private instances (Account: B, Region: west-us-2) using VPC endpoints?

iamaashishpatel
Автор

Awesome. This is exactly what we need. Cool presenter BTW!

hongkang
Автор

Will this work if the regions are different in both accounts ?

bcoaamaykhatri
Автор

@AmazonWebService Thank you for the video. It's been helpful in further understanding it from Private API access perspective.

I tried to do the similar setup using EC2 (Private Subnet) > VPC Endpoint (S3 Interface) > S3 Bucket, but it didn't work somehow.
I had the EC2 SG Inbound Rules set to SSH and HTTPS, didn't change the outbound (Stateful)
Private Subnet RouteTable has an entry to route EC2 outbound traffic (HTTPS) to S3 Bucket via VPCEndpoint (S3 Interface).
I made sure that EC2 and S3 are in the same Region. And CLI has got aws configure profile.
Also, S3 policy has been attached to accept connection from VPCEndpoint-ID (like you've mentioned in the Resource Policy)
When I do following CLI, it hangs and retries : aws s3 ls --region <region-name> --debug
Also, --debug doesn't show where it is failing and why it failing.

Don't know what am I missing in establishing the above private connection from EC2 to S3 via Endpoints (S3 Interface). Any clue?

archprof
Автор

Let me start with AWS sucks. We chose AWS for my org and we are regretting it. I want to use eventbridge from ecs to call api Gateway endpoint and there is absolutely no direct answer given anywhere

VinitKhandelwal