- 新しい順
- 投票が多い順
- コメントが多い順
API Gateway is the name of the service. As such there is only one. You can create multiple APIs in the Gateway.
My recommendation would be to create an API per component. This way you reduce the dependencies between teams.
Once you have multiple APIs, you can place them all behind a single custom domain name so to the clients it seems like a single API.
The design topology is determined by your account structure and resource allocation with the account.Simple answer is, you can have one single API gateway and access it from other AWs accounts. Please refer to the below documentations.
https://aws.amazon.com/premiumsupport/knowledge-center/access-api-gateway-account/ https://aws.amazon.com/blogs/compute/building-private-cross-account-apis-using-amazon-api-gateway-and-aws-privatelink/ https://docs.aws.amazon.com/prescriptive-guidance/latest/modernization-integrating-microservices/api-gateway-pattern.html
関連するコンテンツ
- AWS公式更新しました 2年前
- AWS公式更新しました 2年前
- AWS公式更新しました 2年前