I'm new to AWS and working on a project with strict data-residency requirements. I need to determine whether CloudFront, AWS WAF, and Route 53 can be configured so that their infrastructure and related traffic remain exclusively in the ca-central-1 Region. I understand these services are global, but I'm not sure whether they support regional or geographic restrictions. Are there practical alternatives if they cannot be limited to one AWS Region?
4 Answers
For DNS, the normal managed service will not satisfy a strict single-Region infrastructure requirement because its authoritative name servers are distributed worldwide. Running your own DNS servers in ca-central-1 would give you more placement control, but recursive resolvers and caching systems around the Internet would still be outside Canada. Your domain’s registrar and top-level-domain infrastructure would also remain distributed.
No—not as a complete regional deployment. CloudFront and Route 53 are global services, and their infrastructure is intentionally distributed. CloudFront’s price classes can limit which edge locations serve users, but they do not make the service exclusive to Canada. Route 53 hosted zones use globally distributed authoritative name servers, so you cannot choose ca-central-1 for them.
Geographic restrictions and data residency are different things. CloudFront can restrict which viewers are allowed to access content using geographic rules, but that does not relocate the CDN or guarantee that processing happens only in Canada. Before choosing an architecture, clarify whether the requirement concerns data storage, network transit, service infrastructure, or all of those.
AWS’s compliance documentation and service-specific agreements may allow some globally operated services to be used for regulated workloads. The exact answer depends on the applicable law and contract, so a blanket regional restriction may not actually be required.
If the requirement is that your application infrastructure and stored data stay in Canada, you could deploy the origin and regional components in ca-central-1 and use an Application Load Balancer or Network Load Balancer there, with AWS WAF attached. However, WAF being associated with a Canadian resource does not change the global nature of the service or guarantee that every related control-plane operation occurs in that Region.
It’s worth checking the exact compliance wording. Requirements usually distinguish between stored customer data, request content, logs, metadata, and service control-plane data. DNS generally isn’t required to be hosted in the same Region as the application.

Even if DNS queries are small, the query and response do contain information such as the domain name and returned address. Whether that matters depends on the legal definition of regulated data, so it should be confirmed with the compliance team rather than assumed.