- Newest
- Most votes
- Most comments
Hello There
I understand you detected that AWS CloudFront is providing a Geo restriction to some websites, because Route 53 is using the previous IP's Geolocation DB, So you're seeing geolocation for some of your IP ranges is incorrect in AWS and you want to update it with a correct location.
Please note: CloudFront uses Maxmind tool database to determine the location of the IP's [1], If you find any of your IP's location is shown incorrectly in Maxmind database[2] then you can log a request with Maxmind to correct the location of the IP’s [3].
I suggest that you also view some documentation on CloudFront geographic restrictions feature that lets you control distribution of your content at the country level for all files that you’re distributing with a given web distribution.[4]
I hope this information is helpful.
Best regards,
Mfanelo
Reference: [1]https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_GeoRestriction.html [2]https://www.maxmind.com/en/geoip-demo [3] https://www.maxmind.com/en/geoip-data-correction-request [4]https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/georestrictions.html#georestrictions-geolocation-service
To update AWS CloudFront's geolocation information for your newly rented IP segment, follow these steps: Update WHOIS: Ensure accurate WHOIS details for the new IP segment. Update DNS Records: Update DNS records in AWS Route 53 to reflect new IP addresses when the geolocation data is updated. IP Geolocation DB: Contact third-party geolocation database providers like MaxMind to inform them of the IP segment change. Route 53 Health Checks: Set up health checks in AWS Route 53 to monitor IP availability and performance.
References: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-whois-rdap.html https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-editing.html https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover.html
Relevant content
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago