Host the application in Canada
Place the origin in Canada. The tenant’s origin pool discovers it through owned Canadian Customer Edges, so accepted requests reach the intended application backend.
Canada Topology
See how an F5 Distributed Cloud tenant connects a Canadian origin, serves an application through Toronto and Montreal Regional Edges, and controls access by source country.
Start with the design overview for the request path and controls, then use deployment, verification, and operations for the demonstration lifecycle.
What the tenant configures
Section titled “What the tenant configures”Serve through Canadian Regional Edges
Use the reserved public allocation to advertise the application from Toronto and Montreal Regional Edges. Check the allocation and serving edges to confirm where clients enter.
Control access by source country
Apply a service policy to the actual client source address. Permit sources classified as Canadian and deny other or unknown classifications. Client-supplied forwarding headers don’t change the result.
These checks confirm the configured entry points, origin and source-country decision. They don’t trace every packet between a client and Canada or identify the person behind a source IP address.