1 Answer
- Newest
- Most votes
- Most comments
2
Hi,
You can see at least 3 different reasons for that:
- The geo-blocking features of CloudFront are also intended for legal reasons: some customers do not have legal rights to distribute some content in some regions. It can be used for that.
- WAF is another service which is paid for: some customers need minimal cost. So, CF geo-blocking can be used in that case
- WAF is more flexible than CF re. geo-blocking: in advanced rules, you can combine logically geo-blocking with other conditions on the requester. It's needed by some customer for which CF geo-blocking is then not flexible enough.
Best
Didier
Relevant content
- asked a year ago
- asked 5 years ago
- asked 6 months ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 3 months ago