There is no AWS region in Morocco, and there will not be one in 2026 or 2027. Same for GCP and Azure. If you are building from Morocco, you are picking a region somewhere else, and the choice quietly shapes the cost, the user experience, and what you can legally store where. We have made this choice on a dozen projects in the last two years. Here is the framework we use.
The candidate regions
For a Casablanca-based team serving a Maghreb or French-speaking African user base, the realistic choice is between six regions. Two from AWS, two from GCP, two from Azure, with cross-cloud comparisons where they matter.
| Provider | Region | Code | Location | Distance from Casablanca |
|---|---|---|---|---|
| AWS | Europe (Paris) | eu-west-3 | Paris, France | ~1,900 km |
| AWS | Europe (Spain) | eu-south-2 | Aragon, Spain | ~1,300 km |
| AWS | Middle East (UAE) | me-central-1 | Dubai, UAE | ~5,700 km |
| AWS | Africa (Cape Town) | af-south-1 | Cape Town, ZA | ~7,800 km |
| GCP | europe-west9 | europe-west9 | Paris, France | ~1,900 km |
| GCP | europe-southwest1 | europe-southwest1 | Madrid, Spain | ~1,000 km |
| Azure | France Central | francecentral | Paris, France | ~1,900 km |
| Azure | Spain Central | spaincentral | Madrid, Spain | ~1,000 km |
We have ignored regions further away (us-east-1 etc.) because the latency takes the application out of contention for synchronous user workflows. We have included Cape Town for completeness; it almost never wins for Morocco-served products because the bandwidth path is worse than the distance suggests.
Real latency from Casablanca
These are average round-trip-time measurements taken from three sites in Casablanca (a residential Maroc Telecom fibre line, an office line on Orange Maroc, and a colocation rack at our data centre) to the published public endpoints of each region, mid-May 2026. Numbers are p50 in milliseconds.
| From | eu-south-2 (Spain) | eu-west-3 (Paris) | europe-southwest1 (Madrid) | me-central-1 (UAE) | af-south-1 (Cape Town) |
|---|---|---|---|---|---|
| Maroc Telecom fibre | 38-46 | 52-61 | 32-38 | 145-165 | 195-220 |
| Orange Maroc | 42-50 | 56-65 | 36-44 | 150-170 | 205-225 |
| Colocation (peering) | 28-34 | 41-48 | 24-30 | 135-150 | 180-200 |
Three things to read out of this table:
Spain wins on latency. Both Madrid (GCP, Azure) and Aragon (AWS) consistently deliver sub-50 ms p50 from Maroc Telecom fibre, and below 35 ms with peering. Paris is workable but adds 15-20 ms. UAE and South Africa are not viable for synchronous user workflows from Morocco.
Last-mile dominates. The delta between the residential line and the peered colocation is bigger than the delta between Madrid and Paris. If your users are on Maroc Telecom or Orange Maroc home fibre (which they are), the marginal benefit of a closer cloud region is partly eaten by the local network path. This means: optimising your CDN edge nodes in Morocco itself (Cloudflare, Akamai, and Bunny.net all have Casablanca presence) often delivers more user-perceived speedup than swapping cloud regions.
Peering matters more than published latency. The published peering between major Moroccan ISPs and European cloud regions has improved noticeably in the last 18 months. If you are sensitive to latency at the millisecond level, a quick call with Maroc Telecom Business or with a peering partner like Sparkle (Telecom Italia) can shave 10-15 ms off your worst case.
Cost differences worth knowing
On-demand EC2 c7i.large pricing, hourly rate, mid-May 2026:
| Region | c7i.large | Differential vs eu-west-3 |
|---|---|---|
| eu-west-3 (Paris) | $0.116 | baseline |
| eu-south-2 (Spain) | $0.109 | -6% |
| me-central-1 (UAE) | $0.124 | +7% |
| af-south-1 (Cape Town) | $0.131 | +13% |
Plus the costs that hurt more than the per-hour rate:
Inter-region data transfer. AWS charges $0.02 per GB for data leaving most European regions toward other AWS regions, $0.05-$0.09 per GB for egress to the internet. If your architecture replicates data between Paris and Cape Town for disaster recovery, the monthly bill for that replication line item alone can dwarf the compute savings of picking a cheaper region.
S3 storage class pricing varies by region. S3 Standard is roughly the same across European regions ($0.023 per GB-month). It is materially more expensive in me-central-1 ($0.026) and af-south-1 ($0.027). For a 10 TB archive, that is roughly $40-50 per month difference. Not large, but consistent.
Reserved instance and Savings Plans pricing is roughly uniform across European regions (within 1-2 percent) and meaningfully more expensive in me-central-1 and af-south-1 (5-10 percent premium).
The general rule: stay in Europe for compute, use Africa or Middle East only when there is a regulatory or specific-customer reason. The cost difference is small enough that latency wins.
Compliance: Loi 09-08 plus GDPR overlay
For Moroccan products serving Moroccan users, the relevant data protection law is Loi 09-08 (the Moroccan Personal Data Protection Law). It is broadly similar in shape to GDPR but is enforced by the CNDP (Commission Nationale de Contrôle de la Protection des Données à Caractère Personnel) and has its own specific requirements.
The practical implications for cloud region choice:
Loi 09-08 does not require Moroccan-resident hosting. Unlike some Gulf countries' data residency laws, Loi 09-08 allows international transfer of personal data with appropriate safeguards (typically standard contractual clauses or the recipient country being on the CNDP-approved list). Most European jurisdictions are on that list. Spain, France, and Ireland are all fine.
GDPR applies if you serve EU residents. If any of your users are EU residents (a Moroccan with French residency status, a tourist in Marrakech using your service, anybody in France using a French-language product you market in France), GDPR applies to that processing regardless of where your company is incorporated. You need a Data Processing Agreement with your cloud provider, and the major three (AWS, GCP, Azure) all provide one.
The Moroccan financial sector has stricter rules. Banque Al-Maghrib has issued guidance that effectively requires certain banking workloads to be hosted within Morocco or via specifically-authorised cloud providers operating in-country. If you are building for or with a Moroccan bank, the conversation is not "which European region" but "which Moroccan colocation facility plus which compliant cloud provider".
Practical setup: for non-financial Moroccan products serving Moroccan and European users, the right answer in 2026 is a European region (Paris or Madrid based on latency preference) with a signed DPA, with explicit attention to the data classification process so you know what is and is not personal data under Loi 09-08, and with the CNDP notification done (it is a formality but it is mandatory).
The actual decision
For most Moroccan products in 2026, our recommendation is straightforward:
- Default to eu-south-2 (Spain AWS) or europe-southwest1 (Spain GCP) for compute and primary storage. Best latency. Roughly the cheapest of the viable options. GDPR-compliant. CNDP-acceptable for Loi 09-08.
- Use Cloudflare or Bunny.net CDN with Casablanca PoP for any user-facing static asset or API gateway. This is where the user-perceived speedup actually comes from.
- Add eu-west-3 (Paris) as a secondary or failover region for disaster recovery and for any service that needs more vendor or product breadth than the Spanish regions offer (some AWS services launch in Paris first, in Spain six months later).
- Avoid me-central-1 and af-south-1 unless you have a specific reason. The latency penalty is large, the cost is higher, the vendor service coverage is thinner.
- Talk to your ISP about peering. The latency table above can be improved by 10-15 ms with the right peering arrangement, and your team's cost of doing that conversation is one hour.
If you are working on a bank or telco project with regulatory requirements: this entire analysis changes. Talk to your compliance team first, your architects second, your cloud sales rep last.
What we keep getting asked
"Should we wait for an AWS Morocco region?" No. There is no announcement, no signal, and the historical pace of region rollout in this part of the world is approximately one major launch every five years. Build for the regions that exist.
"What about Outscale / OVH / Scaleway?" Worth considering, especially Scaleway's Paris region, for cost-sensitive workloads or for teams that prefer European sovereignty over American provider scale. Latency is similar to AWS Paris. Service breadth is materially thinner. Good for the right workload, wrong as the default.
"What if we host in Morocco?" Three options exist (N+ONE, Atlas Cloud Services, and AWS's planned local zones with Maroc Telecom partnership which was announced but has not shipped). For Moroccan banking and government workloads, this is increasingly the right answer. For SaaS products, it is operationally heavier and the latency advantage over Spain or Paris is small.
The geographic constraint of building from Casablanca is real, but smaller than it feels. With the right region choice and a CDN strategy, your Moroccan users perceive your service as fast, your European users get good service, and the bill is competitive.
