Hi all, With so many options available ((API Gateway REST API, HTTP API, ALB ) I'm looking for best practices regarding internal service to service communication in a micro service architecture. Specific questions I have: * Which load balancing service to choose when for internal service-to-service communication (API Gateway REST API, HTTP API, ALB)? * What is a best practice for securing internal microservices (just by IP range or OIDC) ?

Best practices for securing service to service REST communication in a microservices architecture

Hi all,

With so many options available ((API Gateway REST API, HTTP API, ALB ) I'm looking for best practices regarding internal service to service communication in a micro service architecture.

Specific questions I have:

Which load balancing service to choose when for internal service-to-service communication (API Gateway REST API, HTTP API, ALB)?
What is a best practice for securing internal microservices (just by IP range or OIDC) ?

トピック

サーバーレスフロントエンド Web & モバイルネットワークとコンテンツ配信マイクロサービス

タグ

Amazon API Gateway マイクロサービス

言語

English

Johannes Langer

質問済み 4年前910ビュー

1回答

新しい順
投票が多い順
コメントが多い順

これらの回答は役に立ちましたか？コミュニティがあなたの知識を活用できるように、正解に賛成票を投じてください。

承認された回答

There are multiple considerations when building microservices. What is a good fit depends on your use case, for instance do you run servers or serverless, is service discovery needed, are the services sync or async in nature or mix - best practice can be different depending on the needs.

I would recommend to read this white paper we have on microservices on AWS https://d1.awsstatic.com/whitepapers/microservices-on-aws.pdf. It will give good overview and lots of context how to approach microservices on AWS.

AWS-User-2851372

回答済み 4年前

Best practices for securing service to service REST communication in a microservices architecture

関連するコンテンツ