Does AWS Have a Region in Kenya? The Complete Answer

No. As of 16 October 2026, Amazon Web Services does not have a full AWS Region in Kenya. There is no Kenya Region code, no group of Kenyan Availability Zones, and no general-purpose regional deployment of services such as Amazon EC2, Amazon S3, Amazon RDS, or AWS Lambda in the country.

AWS does, however, have a meaningful and growing presence in Kenya. Nairobi has three Amazon CloudFront points of presence, Kenya’s first AWS Direct Connect location opened near Nairobi in September 2025, AWS maintains a local business presence, and AWS has announced a Nairobi Local Zone. The Local Zone is not yet generally available and, even when it launches, it will not be the same thing as a full AWS Region.

That distinction matters. An AWS office, edge location, Direct Connect site, Local Zone, and Region perform very different jobs. Seeing “AWS in Nairobi” does not necessarily mean that an application database, S3 bucket, or ordinary EC2 instance can be hosted in Kenya.

The answer at a glance

AWS presence or facility	Status in Kenya	What it means
Full AWS Region	No	Kenya does not have a regional endpoint or multiple AWS Availability Zones.
AWS Availability Zones	No	There are no Availability Zones belonging to a Kenya Region.
AWS Local Zone	Announced, not generally available	AWS lists Nairobi as a future Local Zone, af-south-1-nbo-1a, attached to the Africa (Cape Town) Region.
Amazon CloudFront points of presence	Yes	AWS lists three CloudFront PoPs in Nairobi for caching and delivering content closer to users.
AWS Direct Connect location	Yes	A live site at East Africa Data Centres NBO1 provides private connectivity to AWS.
AWS office or local corporate presence	Yes	AWS has a Kenyan marketing entity and address, but an office is not cloud infrastructure.
AWS Outposts	Potentially, at a customer’s site	Eligible customers can investigate AWS-managed hardware on their own premises; this does not create a public AWS Region.

AWS’s current official list of Regions includes the Africa (Cape Town) Region in South Africa, but no Kenyan Region. The AWS Local Zones location page separately lists Nairobi under Announced, with a “Request interest” action rather than “Get started.”

What an AWS Region actually is

An AWS Region is a separate geographic area in which AWS operates a substantial cluster of cloud infrastructure. Every general-purpose Region has multiple isolated Availability Zones, and each Availability Zone consists of one or more discrete data centres with independent power, networking, and connectivity.

Customers select a Region when they create most AWS resources. A Region has a code—Cape Town is af-south-1, for example—and provides regional endpoints for services. A well-designed application can run across two or three Availability Zones in the same Region so that a failure in one location does not take down the entire system.

Kenya has none of those defining characteristics today:

• There is no Kenya or Nairobi entry in AWS’s Region list.
• There is no Kenyan Region code such as af-east-1.
• There are no Kenyan Availability Zones associated with a Kenyan Region.
• The AWS console does not offer “Africa (Kenya)” as a Region in which customers can create ordinary regional resources.

The only full AWS Region on the African continent is currently Africa (Cape Town), code af-south-1. AWS launched it in April 2020 with three Availability Zones. AWS’s current Region documentation continues to show three Availability Zones for Cape Town and identifies their geography as South Africa.

What AWS does have in Kenya

1. Amazon CloudFront infrastructure in Nairobi

AWS lists three Amazon CloudFront points of presence in Nairobi on its CloudFront features and locations page. CloudFront is AWS’s content delivery network. It can cache websites, video, software downloads, images, and other cacheable responses near viewers, reducing the distance that every request must travel to an origin server.

This can materially improve the experience of Kenyan users even when the origin is an S3 bucket, load balancer, or web server in Cape Town, Bahrain, the UAE, Europe, or elsewhere. CloudFront can also terminate HTTPS connections at the edge, integrate with AWS WAF and AWS Shield, and run lightweight logic through CloudFront Functions.

A CloudFront PoP is not a Region, however. It does not give customers the full regional service catalogue. You cannot choose “Nairobi” as the Region for an S3 bucket, RDS database, ECS cluster, or normal Lambda function merely because CloudFront has edge servers there. CloudFront also cannot eliminate the origin round trip for every request: uncached content, writes, personalised responses, database calls, and many API requests still have to reach the origin.

CloudFront should therefore be understood as a delivery layer, not a Kenyan replacement for a full application Region.

2. An AWS Direct Connect location near Nairobi

On 3 September 2025, AWS opened Kenya’s first AWS Direct Connect location at East Africa Data Centres NBO1 near Nairobi. According to the AWS launch announcement, it offers dedicated 10 Gbps and 100 Gbps connections, with MACsec encryption available.

Direct Connect lets an organisation establish private physical network connectivity from its office, data centre, or colocation environment to AWS. It can provide more predictable throughput and a more consistent network path than the public internet. With the appropriate virtual interfaces and Direct Connect Gateway design, customers can reach public AWS Regions outside China and other AWS locations.

Again, a Direct Connect site is not a Region and not a hosting location. It is an on-ramp to AWS’s network. Connecting at NBO1 does not mean that the destination EC2 instance or database is in Kenya. If the workload runs in af-south-1, its regional resources remain in South Africa; the Nairobi location is the point at which the customer’s private connection enters the AWS network.

3. An announced Nairobi AWS Local Zone

AWS has announced a Local Zone for Nairobi with the intended zone name:

af-south-1-nbo-1a

The name reveals two important facts. nbo refers to Nairobi, while the af-south-1 prefix shows that its parent Region is Africa (Cape Town). But the zone remains in the Announced section of the official AWS Local Zones page, not the generally available section. AWS currently offers a form to register interest rather than a console link to start deploying.

Until AWS announces general availability, organisations should not design a committed production launch around the assumption that this Local Zone can be used by a particular date. AWS has not published a firm launch date on the location page.

When available, a Local Zone would place a subset of AWS compute, storage, database, and other services closer to Nairobi users. A customer would extend a VPC from the Cape Town parent Region into a Nairobi subnet and deploy only the resources supported in that Local Zone.

Even then, the Nairobi Local Zone would not become a Kenyan AWS Region:

• It would remain attached to the Cape Town Region.
• It would offer a smaller service and instance selection than a Region.
• Some control-plane operations and application dependencies would remain in the parent Region.
• A single Local Zone would not provide the same in-country multi-Availability-Zone architecture as a full Region.
• Data would remain in Kenya only for resources and traffic paths specifically designed to do so; using the Local Zone would not automatically make an entire system Kenya-resident.

Teams should check service availability, quotas, pricing, network paths, failure modes, and data location again when AWS declares the zone generally available.

4. A Kenyan AWS business presence

AWS’s marketing-entity directory lists AWS Kenya Limited and a Nairobi address. Local teams, partner activity, training, sales, and customer support are evidence of AWS’s commercial investment in the country.

They do not establish a Region. Corporate presence and physical cloud infrastructure are separate facts. The address of an AWS office, the entity named on a contract, and the physical location in which customer content is processed may all be different.

5. Hybrid options such as AWS Outposts

For organisations that need AWS infrastructure at a Kenyan site, AWS Outposts may be worth evaluating. Outposts places AWS-managed racks or servers in a customer’s data centre or colocation facility and connects them to a parent AWS Region. It is intended for workloads with low-latency access to on-premises systems, local processing needs, or particular residency requirements.

Outposts is dedicated hybrid infrastructure, not a public Kenyan Region. It requires suitable premises, connectivity, capacity planning, supported services, and a commercial engagement with AWS. Customers also have to understand which data and control-plane functions remain local and which interact with the parent Region.

Region vs. Local Zone vs. edge location vs. Direct Connect

The easiest way to avoid confusion is to ask what each facility is designed to do.

Infrastructure type	Primary purpose	Typical customer resources	Kenya status
AWS Region	Full cloud hosting in a geography, with multi-AZ resilience	EC2, S3, RDS, Lambda, EKS, analytics, AI, and many other services	Not present
Availability Zone	Isolated failure domain inside a Region	Subnets, instances, databases, load balancer nodes	Not present as part of a Kenya Region
Local Zone	Selected services close to a metro area, managed through a parent Region	Selected EC2/EBS and other supported resources	Nairobi announced; not yet generally available
CloudFront PoP	Cache and deliver content and perform limited edge functions	Cached objects, request handling, CDN security integrations	Three PoPs listed in Nairobi
Direct Connect location	Private network entry point	Physical connections and virtual interfaces	Available near Nairobi
Outposts	AWS infrastructure at a customer’s location	A supported subset of AWS services on dedicated hardware	Customer-specific, subject to eligibility

This is why all of the following statements can be true at once: AWS has infrastructure in Kenya; AWS has a business presence in Kenya; AWS can improve delivery performance for Kenyan users; and AWS still does not have a Region in Kenya.

Where should a Kenyan organisation host its AWS workload?

There is no universal best Region. Kenyan teams should create a shortlist and test it against the workload rather than assuming that the Region with “Africa” in its name will always win.

Africa (Cape Town), af-south-1

Cape Town is the only full AWS Region in Africa and is the parent Region named for the announced Nairobi Local Zone. It is a natural starting point for many East African deployments and offers three Availability Zones. It may also simplify a future architecture that extends selected components into the Nairobi Local Zone.

However, Cape Town is still in South Africa, not Kenya. A Kenyan organisation using it is transferring relevant customer content outside Kenya. Service availability, pricing, network routing, and measured latency should all be checked rather than inferred from the Region’s name.

The Cape Town Region is opt-in for AWS accounts, so an administrator may need to enable it before use.

Middle East Regions

The Middle East (Bahrain) Region, me-south-1, and Middle East (UAE), me-central-1, can be credible candidates for East African applications. Actual latency depends on an internet provider’s peering and cable routes, not just straight-line distance. They may differ from Cape Town in service coverage, price, and network performance.

European Regions

Europe (Frankfurt), eu-central-1, and Europe (Ireland), eu-west-1, are often considered when a team needs broad service availability, existing organisational infrastructure, or integration with European systems. The trade-offs can include a longer network path for Kenyan users and an additional cross-border compliance analysis.

A sound selection process

Evaluate candidate Regions using the following order:

1. Legal and data-location constraints. Identify what data the system processes and whether it may leave Kenya.
2. Required services and features. Confirm every service, instance family, database engine, AI model, and feature in AWS’s current regional availability tables.
3. Measured network performance. Test from the mobile and fixed networks actually used by customers. Record median and tail latency, packet loss, throughput, DNS time, TLS setup time, and application response time over several days.
4. Availability design. Use at least two Availability Zones for production systems that require high availability. Decide whether disaster recovery must use a second Region.
5. Total cost. Compare compute, managed services, inter-AZ traffic, internet egress, support, taxes, Direct Connect, backup, and disaster-recovery costs—not just an EC2 hourly rate.
6. Operational fit. Consider team skills, support coverage, existing landing zones, security tooling, and dependencies in other Regions.

Do not select a Region from a single public ping test. ICMP results may not represent HTTPS, private connectivity, mobile networks, or the behaviour of the complete application.

A practical architecture for serving users in Kenya today

For a typical public web or mobile application, a sensible starting design is:

Kenyan users
     |
     v
Route 53 / AWS WAF / Amazon CloudFront
     |
     |  Cached content served near users when possible
     v
Application Load Balancer or API endpoint
     |
     v
Application across 2–3 Availability Zones in the selected AWS Region
     |
     +--> Multi-AZ database
     +--> Object storage and backups
     +--> Monitoring, logging, and security services

This approach uses Nairobi edge capacity for suitable content while keeping the origin highly available in a full Region. Static assets should have deliberate cache headers and versioned filenames. Dynamic endpoints should minimise chatty client-server interactions, compress responses, reuse connections, and avoid serial calls across long distances.

Enterprises with private networks can add the Nairobi Direct Connect location, normally with redundant connections and a backup VPN. Direct Connect alone is not a resilience strategy: the design should account for device, circuit, provider, location, and regional failures.

If strict Kenyan processing is required today, a hybrid design may be necessary. Locally hosted infrastructure or an eligible Outposts deployment can handle the regulated or latency-sensitive portion, while permitted services run in an AWS Region. This increases architectural and operational complexity, so the boundary between local and regional data must be explicit.

Data residency and Kenyan law

The absence of a Kenyan AWS Region does not mean that Kenyan organisations are categorically prohibited from using AWS. It does mean that they must treat data location as a design and governance decision.

Part VI of Kenya’s Data Protection Act addresses transfers of personal data outside Kenya. Section 48 permits cross-border transfers only under specified conditions, including appropriate safeguards or listed grounds of necessity. Section 49 imposes additional requirements for sensitive personal data, including consent and confirmation of appropriate safeguards. Section 50 allows certain processing to be prescribed for a server or data centre in Kenya.

The Data Protection (General) Regulations, 2021 add detail on transfer mechanisms and data localisation. The Office of the Data Protection Commissioner also publishes guidance on cross-border transfers, data protection impact assessments, and sector-specific processing.

In practice, a Kenyan data controller or processor should:

• Inventory the personal, sensitive, regulated, and operational data in the workload.
• Determine where primary data, replicas, backups, logs, caches, support data, and encryption keys will be processed or stored.
• Establish and document a lawful transfer mechanism and appropriate safeguards before transferring personal data abroad.
• Review sector-specific requirements for finance, health, government, education, telecommunications, transport, and other regulated activities.
• Conduct a data protection impact assessment when the processing is likely to create high risk.
• Put suitable controller-processor terms and security requirements in place.
• Apply least privilege, encryption in transit and at rest, key-management controls, logging, retention rules, and tested deletion procedures.
• Reassess the design when adding CloudFront, a SaaS integration, support access, cross-Region replication, analytics, or generative AI, because each can change the data flow.

AWS publishes Kenya-specific guidance on the Data Protection Act and provides compliance reports through AWS Artifact. Those resources can support a compliance programme, but using AWS does not make a customer automatically compliant. Under the shared-responsibility model, the customer remains responsible for its workload configuration, access controls, data classification, lawful basis, transfer assessment, and many other controls.

This section is general technical information, not legal advice. Organisations handling regulated or strategic data should obtain advice based on their sector and facts.

Does CloudFront make data “hosted in Kenya”?

Not in the ordinary sense of hosting an application in a Region.

CloudFront may cache copies of selected content at an edge location near viewers, including Nairobi. The authoritative origin, database, application compute, logs, and backups can still be outside Kenya. Cache misses and uncacheable requests still reach that origin. AWS, rather than the customer, selects the edge location that serves a viewer, and CDN behaviour can change with routing and availability conditions.

For a marketing site, media library, or software download, local caching may be exactly what is needed. For a rule that requires a complete serving copy of specified personal data in Kenya, a transient CDN cache is unlikely to be an adequate substitute for a deliberately designed local data store. Confirm the legal and technical interpretation for the particular requirement.

Does Direct Connect keep data in Kenya?

No. Direct Connect controls the network path into AWS; it does not determine the location of the destination workload.

A packet can enter the AWS network at the Nairobi Direct Connect site and continue to an EC2 instance, S3 bucket, or database in Cape Town or another Region. Direct Connect may improve privacy of the transport path, consistency, and throughput, but it does not convert an overseas Region into a Kenyan one and does not by itself satisfy a localisation requirement.

Will the Nairobi Local Zone solve data residency?

It may help some use cases after it becomes available, but it should not be treated as a universal solution.

The answer will depend on which services launch in Nairobi, where each service stores data and backups, which operations rely on Cape Town, and whether the architecture maintains a required copy in Kenya. Local Zones usually support a selected subset of services, while applications continue using regional services in the parent Region.

Before relying on the future zone for residency, obtain a data-flow diagram and service-by-service confirmation covering:

• Compute disks, snapshots, images, and backups
• Managed databases and their replicas
• Object storage
• Load balancing and public IP addressing
• Identity, keys, secrets, logs, metrics, and audit trails
• Control-plane metadata
• Failure behaviour when the Local Zone or its link to the parent Region is unavailable

Cost and billing considerations for Kenyan customers

AWS prices vary by Region and service. A design that appears inexpensive can become costly once internet egress, inter-Availability-Zone traffic, managed NAT gateways, backups, CloudFront requests, logs, support, and private connectivity are included.

For accounts located in Kenya, AWS states on its Kenya tax help page that AWS Europe charges Kenyan VAT on service charges and directs customers to maintain the correct tax registration number and address in Billing settings. Tax treatment and rates can change, so finance teams should verify the current invoice entity, recoverability of VAT, withholding obligations, foreign-currency exposure, and procurement rules rather than relying on an old estimate.

The announced Nairobi Local Zone will have its own pricing when it becomes available. Local Zone compute and data-transfer economics should be compared with regional hosting plus CloudFront, not assumed to be cheaper simply because the hardware is closer.

Common misconceptions

“AWS has servers in Nairobi, so Nairobi must be a Region.”

False. CloudFront PoPs and Direct Connect equipment are AWS infrastructure, but neither is a Region.

“The Nairobi Local Zone code means it is already live.”

False. AWS has published the intended code, af-south-1-nbo-1a, but currently lists the location as announced and invites customers to register interest.

“A Local Zone is just a smaller independent Region.”

False. A Local Zone is an extension of a parent Region, offers selected services, and relies on that Region for parts of its operation.

“Cape Town keeps Kenyan data in Kenya because both countries are in Africa.”

False. Data in the Cape Town Region is in South Africa. Data-protection obligations are based on national jurisdictions and the actual data flow, not the continent name in the AWS console.

“CloudFront removes all latency to the origin.”

False. It can serve cache hits locally and accelerate delivery, but dynamic requests, writes, and cache misses still depend on the origin and application design.

“Direct Connect means the application runs at the connection site.”

False. Direct Connect is private connectivity to AWS resources located elsewhere unless a separate local compute platform is part of the architecture.

How to verify the answer yourself

AWS’s footprint changes, so verify current status before making a procurement or compliance decision:

1. Check the AWS Regions documentation for an official Kenya Region and Region code.
2. Check the AWS Local Zones locations page and see whether Nairobi appears under “Generally Available” or “Announced.”
3. Check the available Local Zones documentation, which lists deployable zones and their parent Regions.
4. Check CloudFront’s current PoP list for Nairobi edge coverage.
5. Check the AWS Direct Connect locations page for current facilities and port speeds.
6. Confirm service availability and data-location behaviour in writing for regulated workloads.

Be precise with the question. “Does AWS have infrastructure in Kenya?” has a yes answer. “Can I select a full Kenya AWS Region and deploy a multi-AZ regional workload there?” currently has a no answer.

Frequently asked questions

What is the AWS Region code for Kenya?

There is none because Kenya does not have an AWS Region. af-south-1 is the code for Africa (Cape Town) in South Africa, not Kenya.

What is the code for the announced Nairobi Local Zone?

AWS lists af-south-1-nbo-1a. Its parent Region is af-south-1, Africa (Cape Town). The code has been announced, but the Nairobi zone is not yet generally available.

Can I launch an EC2 instance in Nairobi today?

Not in a public AWS Region or generally available AWS Local Zone. An organisation could separately investigate an on-premises or colocation deployment such as AWS Outposts, subject to AWS availability and commercial requirements.

Can I create an S3 bucket in Kenya?

No. S3 buckets are created in supported AWS Regions, and Kenya is not one of them. CloudFront may cache S3 objects at Nairobi edge locations, but the S3 bucket itself remains in its selected Region.

Which AWS Region is best for Kenya?

Often the shortlist begins with Cape Town, Bahrain, the UAE, and sometimes a European Region. The best choice depends on lawful data location, measured latency from the relevant Kenyan networks, required services, resilience, price, and organisational constraints.

Is Cape Town the nearest AWS Region to Nairobi?

Do not use geographic distance as a proxy for network performance. Internet routes do not follow straight lines, and performance varies by ISP, carrier, time, and destination. Benchmark Cape Town and other viable Regions from the networks your users actually use.

Does AWS have data centres in Kenya?

AWS publicly confirms CloudFront PoPs and a Direct Connect location in the Nairobi area, and it has announced a Local Zone. Those facts should not be restated as a full general-purpose AWS data-centre Region. AWS also generally avoids publishing detailed addresses and layouts for its secure infrastructure.

When will the Nairobi Local Zone launch?

AWS’s current location page does not provide a firm general-availability date. Treat any unofficial date as speculation until AWS publishes a launch announcement and moves Nairobi into its generally available list.

Final verdict

AWS does not currently have a Region in Kenya. The full regional option on the continent is Africa (Cape Town), af-south-1, in South Africa.

Kenya nevertheless has an important AWS footprint: three CloudFront PoPs in Nairobi, a live Direct Connect location near Nairobi, a local business presence, and an announced Nairobi Local Zone tied to Cape Town. These capabilities can improve content delivery, private connectivity, and—once the Local Zone launches—selected low-latency or local-processing workloads. None should be described as a Kenyan AWS Region.

For most teams, the practical strategy today is to select a full AWS Region using legal, service, latency, resilience, and cost criteria; use CloudFront to serve Kenyan users efficiently; consider Direct Connect for enterprise private connectivity; and design hybrid local processing where genuine Kenyan residency is required. Revisit that architecture when AWS formally announces general availability and publishes the supported services for the Nairobi Local Zone.

---

Infrastructure status verified against official AWS and Kenyan sources on 16 October 2026. AWS services, locations, pricing, and legal requirements can change.