最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

amazon web services - AWS WAF Not Working with Global Accelerator Static IPs for ALB Restriction - Stack Overflow

programmeradmin1浏览0评论

We have a frontend Next.js application running on AWS ECS behind an Application Load Balancer. To get a static IP for this ALB, we use AWS Global Accelerator in front of it.

On the backend, we have an API running on ECS, also behind an ALB. We want to restrict API access to only our frontend ALB by using AWS WAF in front of the API ALB.

What We Did: We whitelisted the static IPs assigned to our frontend's Global Accelerator in AWS WAF. However, AWS WAF does not seem to recognize requests as coming from those static IPs, causing all requests to be blocked.

What We Observed: When analyzing traffic logs, WAF sees different IPs instead of the Global Accelerator's static IPs.

  1. Is restricting API access to only our frontend ALB using AWS WAF and Global Accelerator achievable, or are we approaching this incorrectly?

  2. Is there a better way to enforce access control between our frontend ALB and backend ALB without relying on IP-based filtering?

发布评论

评论列表(0)

  1. 暂无评论