AWS opens Bogotá Local Zone, joining a network of more than 30 locations
AWS announced general availability of the Bogotá, Colombia Local Zone on November 20, 2026. The facility brings selected AWS services closer to metropolitan users and is designed for workloads with single-digit millisecond latency needs.

AWS says its Local Zone network spans more than 30 locations worldwide.1
AWS describes the Bogotá zone as intended for workloads needing single-digit millisecond latency.1
The Bogotá location supports EC2 instances from the C7i, M7i and R7i families.1
Story
What AWS’s Bogotá Local Zone providesAmazon Web Services announced that its Local Zone in Bogotá, Colombia, had reached general availability on November 20, 2026, making the location available for customer use.1 The announcement adds Bogotá to a Local Zone network that AWS says spans more than 30 locations around the world.1 The figure describes the overall reach of Local Zones, not the number of locations in Colombia or the number of zones in Bogotá.1 AWS presents the new zone as an option for applications whose performance requirements call for single-digit millisecond latency.1 For customers whose workloads fit that latency profile, general availability means the Bogotá location is now available for use rather than merely announced as a future offering.1
Local Zones are designed to position computing, storage, networking, and a selection of other AWS services nearer to metropolitan areas.1 They use the same application programming interfaces and tools available with AWS Regions, according to the company.1 That combination distinguishes the offering in the announcement: services are placed closer to a city while customers continue to work with familiar AWS interfaces.1 AWS names examples including interactive games, live video broadcasts, medical-image work, and financial transaction processing as workloads that may require the stated latency range.1 The examples show that the latency target is relevant to several different kinds of work, while the shared APIs and tools apply across the Local Zone offering.1
Those examples span several kinds of applications, but AWS describes them together in terms of their need for very low latency rather than as a single industry.1 The announcement does not provide measured latency results for the Bogotá zone or report performance tests for any of the named workloads.1 It therefore specifies the intended workload profile without quantifying how quickly a particular application will operate from the new location.1 The stated scope is the Bogotá Local Zone and the services AWS lists as supported there, rather than every service offered through AWS Regions.1 The named examples indicate who might benefit in principle, but AWS's description gives no measured result for any one of those users or workloads.1
For computing, the Bogotá zone supports Amazon EC2 instances from the C7i, M7i, and R7i families.1 The listed storage options include S3 One Zone-Infrequent Access and EBS volumes in gp3, gp2, and io1 types, with local snapshots.1 AWS also names its ECS and EKS container services, along with VPC, Direct Connect, and Application Load Balancer, among the supported offerings.1 The list identifies specific products and instance families; it does not state that every AWS service is available in the Bogotá location.1 Customers can therefore assess the listed compute, storage, and networking components against their needs, but the announcement limits its support claims to the named services and families.1
Customers who want to enable the zone can select the code us-east-1-bog-1a in the Regions and Zones area of AWS Global View.1 AWS gives a second route: customers can make the selection by calling the ModifyAvailabilityZoneGroup API.1 These are the two enablement methods named in the announcement, and both concern selecting the Bogotá zone for use.1 AWS does not describe additional activation steps in the supplied announcement details.1 The choice between the listed routes is an interface selection or an API call; AWS identifies no other enablement method in its announcement.1
AWS says Local Zone customers are charged for what they use and are not required to accept a minimum commitment.1 The company lists On-Demand, Savings Plans, and Spot Instances as pricing choices for the Bogotá location.1 This describes the available payment approaches, but the announcement does not provide prices or compare the cost of those approaches.1 For specific Bogotá rates, AWS directs customers to its Local Zones pricing page.1 The no-minimum-commitment terms and three listed pricing options give customers alternatives, but they do not establish which option would cost less for a particular workload.1
The announcement does not give a customer count, usage forecast, or estimate of how many applications might run in Bogotá.1 Its description of affected users is instead framed around workloads that need the specified latency, with examples drawn from gaming, video, medical imaging, and finance.1 The more-than-30 figure applies to AWS Local Zone locations worldwide, while the Bogotá announcement identifies one particular new location.1 Neither figure measures the number of customers, the volume of services used, or the performance change experienced by an individual customer.1 As a result, the announcement establishes the scale of the global Local Zone network and the kind of workload targeted, but not how many people or organizations will use Bogotá.1
AWS’s announcement presents the Bogotá launch as a general-availability release and describes the products and methods customers can use to access it.1 For background on the wider service, the company points readers to its Local Zones overview page.1 The announcement supplies a pricing-page reference as well, separating general pricing choices from the location-specific details available there.1 Taken together, the details define the change as a new metropolitan deployment with named computing, storage, networking, and application services, rather than a stated expansion of every AWS offering.1 The overview and pricing page serve different purposes in the information AWS provides: one explains Local Zones generally, while the other supplies Bogotá pricing details.1
The practical choice described by AWS is whether a workload fits the low-latency use cases it names and whether the listed Bogotá services meet its needs.1 Customers can consult the overview for information about the broader Local Zones service and the pricing page for rates tied to the Bogotá location.1 The announcement provides no specific latency measurements, adoption figures, or price amounts with which to compare the new zone against another AWS location.1 Its stated change is therefore geographic availability: Bogotá is now a generally available Local Zone within a global network of more than 30 locations.1 For prospective users, the announcement offers details to evaluate service fit and pricing sources, but no quantified basis for comparing performance or adoption across locations.1
Structure
Who is connected to whom- 1Amazon Web Services
- uses →Fact
- ← customer ofFact
- ← part ofFact
- ← partners withFact
- supplies →Fact
History
How it came to this- November 20, 2026Bogotá Local Zone reaches general availabilityAWS announced that customers can use the Bogotá Local Zone.
- NowNovember 20, 2026 AWS Bogotá Local Zone general availability
Impact
Spreading outward, level by level- Level 1Workloads seeking low latency
The zone is intended for workloads requiring single-digit millisecond latency, including the application examples AWS names.1
Fact - Level 2Available AWS services
The location supports specified EC2 instance families and named storage, container, networking and load-balancing services; the announcement does not claim that every AWS service is available there.1
Fact - Level 3Customer access
Customers can enable the location through AWS Global View or the ModifyAvailabilityZoneGroup API, using the zone code AWS specifies.1
Fact - Level 4Potential local performance
Customers with suitable latency-sensitive workloads in Bogotá may be able to run them locally, but the announcement provides no measured latency results.
Analysis
Sources
What each source supportsWritten by AI from the sources listed below: every fact was checked word for word against its source, and inference is marked apart. How we write