3 個答案
- 最新
- 最多得票
- 最多評論
0
Hi,
An HTTP 403
error shouldn't be related to the IP reputation. It usually means that you're asking something that the server is refusing to send to you. Usually this is related to a permissions issue or not being authorized to request the file you're asking for.
Here you can read more information:
Hope that helps.
已回答 2 年前
0
Hello,
Unfortunately we have no public-facing tool to check what IP Addresses are in the AWS Managed Rules - Amazon IP Reputation List.
已回答 2 年前
0
Hi, I know it's been a long time, but did you solve the ip reputation list problem? apparently I have exactly the same problem as you, there are two managed rules that block IPs, GeoGuard and ReputationIPList, I solved the blocking with GeoGuard but with ReputationIPList still not.
已回答 9 個月前
相關內容
- 已提問 6 個月前
- AWS 官方已更新 10 個月前
- AWS 官方已更新 1 年前
Thanks for the response!
To expand, the 403 errors we are noticing are not happing with one specific site/server, its happening globally across multiple cloudfront hosted sites, all different with no relation to each other.
Its mitigated by swapping our external IP (but only temporarily), which is kind of why I have been going down the path of IP Reputation, and trying to narrow down if we are being throttled, as we do have high Connections per second of (legitimate) traffic to AWS.