マイクロサービス時代の認証と認可 - AWS Dev Day Tokyo 2018 #AWSDevDay都元ダイスケ Miyamoto
マイクロサービスが話題を集め、コンポーネントの急速な API 化が進んでいます。
認証や認可は、主にエンドユーザとシステムの間の問題だと認識されますが、今やコンポーネント間のサービス呼び出しにおいても重要な役割を担っています。
複雑に入り組んだマイクロサービス間の認証と認可について、実際に開発している API プラットフォームの実例を元に、実践的な知見をお伝えします。
The document discusses Amazon Route 53 and Route 53 Resolver for hybrid cloud DNS. It explains that Route 53 Resolver allows DNS queries to be resolved between on-premises networks and AWS resources using private and public DNS zones. It provides examples of configuring inbound and outbound endpoints to allow resolution of queries from VPCs and on-premises to internet domains and private domains. The document also mentions additional capabilities like resolving queries for internal domain names in a VPC.
This document discusses the need for a service mesh and introduces AWS App Mesh as a service mesh solution. It explains that as applications become more distributed, microservices-based, and utilize different technologies, a common way to handle communication between services is needed to ensure reliability, security, and observability across the system. A service mesh provides this by managing traffic at the infrastructure level rather than requiring each application to implement its own communication logic.
マイクロサービス時代の認証と認可 - AWS Dev Day Tokyo 2018 #AWSDevDay都元ダイスケ Miyamoto
マイクロサービスが話題を集め、コンポーネントの急速な API 化が進んでいます。
認証や認可は、主にエンドユーザとシステムの間の問題だと認識されますが、今やコンポーネント間のサービス呼び出しにおいても重要な役割を担っています。
複雑に入り組んだマイクロサービス間の認証と認可について、実際に開発している API プラットフォームの実例を元に、実践的な知見をお伝えします。
The document discusses Amazon Route 53 and Route 53 Resolver for hybrid cloud DNS. It explains that Route 53 Resolver allows DNS queries to be resolved between on-premises networks and AWS resources using private and public DNS zones. It provides examples of configuring inbound and outbound endpoints to allow resolution of queries from VPCs and on-premises to internet domains and private domains. The document also mentions additional capabilities like resolving queries for internal domain names in a VPC.
This document discusses the need for a service mesh and introduces AWS App Mesh as a service mesh solution. It explains that as applications become more distributed, microservices-based, and utilize different technologies, a common way to handle communication between services is needed to ensure reliability, security, and observability across the system. A service mesh provides this by managing traffic at the infrastructure level rather than requiring each application to implement its own communication logic.