Skip to content
Kuza Ndoto Academy

Regions, Availability Zones & Edge Locations

Beginner → IntermediateChapter 1 · Page 3 of 304 min readUpdated 15 Nov 2026

AWS runs data centres all over the world, organised into Regions, Availability Zones and edge locations. Understanding this layout helps you choose where to run your app, keep it online when something fails and make it fast for your users.

Regions

A Region is a separate geographic area where AWS runs a cluster of data centres, such as eu-west-1 (Ireland), us-east-1 (N. Virginia) or af-south-1 (Cape Town). AWS operates dozens of Regions and keeps adding more. Each Region is independent: resources you create in one Region stay there unless you copy them elsewhere, which helps with data residency rules.

For learners in East Africa, Africa (Cape Town), af-south-1 is the closest AWS Region. Even so, network traffic from Nairobi or Kampala to Cape Town still travels a long way, so latency is noticeably higher than for users in South Africa. Some teams in the region choose a European Region such as Ireland or Frankfurt because of undersea cable routes and wider service availability. Measure from where your users are before deciding.

Opt-in Regions

Older Regions are enabled for every account automatically. Newer ones, including Cape Town, are opt-in: you must enable them in your account settings before you can use them. In the console, open the account menu, choose Account, find AWS Regions and enable the Region. You can also check from the CLI. The output below is an example and is shortened:

aws account list-regions --region-opt-status-contains ENABLED ENABLING DISABLED \
    --query "Regions[?RegionName=='af-south-1']"
[ { "RegionName": "af-south-1", "RegionOptStatus": "DISABLED" } ]
aws account enable-region --region-name af-south-1

Enabling a Region can take a few minutes to complete.

Availability Zones

Each Region contains several Availability Zones (AZs), usually three or more. An AZ is one or more data centres with their own power, cooling and networking, located far enough from the other AZs that a flood or power cut is unlikely to hit two at once, but close enough to be joined by fast, low-latency private links. AZ names add a letter to the Region name. This example lists the AZs in Cape Town (your output may differ):

aws ec2 describe-availability-zones --region af-south-1 \
    --query "AvailabilityZones[].ZoneName"
[ "af-south-1a", "af-south-1b", "af-south-1c" ]

The key design rule is: for anything important, use at least two AZs. If one AZ has a problem, your app keeps running in the other. Load balancers, Auto Scaling groups and databases such as RDS Multi-AZ are built to make this easy.

Region: af-south-1 (Cape Town) AZ af-south-1a Data centre Data centre AZ af-south-1b Data centre Data centre AZ af-south-1c Data centre Data centre Edge locations Edge location Edge location Edge location CloudFront, Route 53 near your users
Figure 1. A Region holds several isolated Availability Zones joined by fast private links; each AZ has one or more data centres. Edge locations are separate, smaller sites spread across many cities to cache content and answer DNS close to users.

Edge locations and other sites

  • Edge locations are small sites in many more cities than there are Regions, including several in Africa. Amazon CloudFront uses them to cache copies of your content near users, and Route 53 uses them to answer DNS queries quickly.
  • Local Zones place selected services in a large city, closer to users than the parent Region, for latency-sensitive apps.
  • AWS Outposts puts AWS-managed hardware inside your own building, for workloads that must stay on-premises.

Global, regional and zonal services

ScopeMeaningExamples
GlobalNot tied to one RegionIAM, Route 53, CloudFront
RegionalLives in one Region, spread across its AZs by AWSS3 buckets, DynamoDB tables, Lambda functions
ZonalLives in one specific AZEC2 instances, EBS volumes, subnets
Common mistake

"My server disappeared!" Usually it has not; the console is simply showing a different Region. The Region selector sits in the top-right of the console. If you cannot find a resource, check the Region first. Forgotten resources in a Region you rarely look at are also a common cause of surprise bills.

Choosing a Region

  1. Data rules: does the law or your client require data to stay in a certain country or continent?
  2. Latency: which Region is fastest for your users? Test it.
  3. Service availability: not every service or feature is in every Region. Check the AWS "Services by Region" list.
  4. Price: the same service can cost different amounts in different Regions.

Key points

  • A Region is a geographic area; it contains several isolated Availability Zones made of one or more data centres.
  • Spread important workloads across at least two AZs for high availability.
  • Edge locations bring CloudFront and Route 53 close to users worldwide.
  • Cape Town (af-south-1) is AWS's African Region; it is opt-in and must be enabled first.
  • Choose a Region based on data rules, latency, service availability and price.
Up next · Cloud FoundationsCreating an AWS Account SafelySign up, secure the root user, use the Free Tier and set billing alerts.
→

Tip: use the ← and → keys to move between pages.