- 新しい順
- 投票が多い順
- コメントが多い順
There's a lot to unpack here and this answer won't do it justice - I strongly recommend that you reach out to your local AWS Solutions Architect who can have a conversation with you in depth about this. If they can't, they can find a networking expert who can. That said:
I would always use an API Gateway instead of a firewall for API Gateway "type tasks" for many reasons. First, API Gateway is scalable and you only pay for what you use. You also get very find-grained controls down to the method level. You can modify requests and check for specific attributes - all without scaling your back end.
But: If you're dealing with other types of traffic (non HTTP) then a firewall might be the best choice.
You're right, API Gateway won't do everything for you. But neither will a firewall.
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 1年前
- AWS公式更新しました 10ヶ月前