AWS announces preview of AWS Interconnect - multicloud

AWS announces AWS Interconnect – multicloud (preview), providing simple, resilient, high-speed private connections to other cloud service providers. AWS Interconnect - multicloud is easy to configure and provides high-speed, resilient connectivity with dedicated bandwidth, enabling customers to interconnect AWS networking services such as AWS Transit Gateway, AWS Cloud WAN, and Amazon VPC to other cloud service providers with ease.

Is there any limitation with AWS PrivateLink?

I'm implementing a model-based system User -> AWS API Gateway -> AWS PrivateLink -> Network Load Balancer -> EC2 (Apache with PHP). When I load test with the NLB endpoint directly there is absolutely no problem with high load. But when testing with the API Gateway endpoint I get a lot of 500 error codes, Execution failed due to a network error communicating with the endpoint: Connection is closed, execution failed due to a timeout error (although it's a timeout error I get an error after very fast time). I'm wondering if there's something wrong with AWS PrivateLink? Can someone help me, thanks

주제: 서버리스 프론트엔드 웹 및 모바일 네트워킹 및 콘텐츠 전송
태그: 아마존 API 게이트웨이 네트워크 로드 밸런서 탄력적 로드 밸런싱 AWS 프라이빗 링크 네트워킹 및 콘텐츠 전송
언어: English

iamnick

질문됨 3년 전424회 조회

1개 답변

최신
최다 투표
가장 많은 댓글

수락된 답변

This is a situation where I would create a support case. It looks like everything (on the NLB->EC2 side) is operating correctly given your testing; so definitely worthwhile having the support team look into the details of API Gateway and see what is happening.

전문가

Brettski-AWS

답변함 3년 전

전문가

Giovanni Lauria

검토됨 2년 전

Is there any limitation with AWS PrivateLink?

답변 추가

관련 콘텐츠