> For the complete documentation index, see [llms.txt](https://notebook.iuriioapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notebook.iuriioapps.com/cloud/aws/high-availability/global-infrastructure.md). # Global Infrastructure The AWS Global Infrastructure builds around **Regions** and **Availability Zones**. So far, there are: * 65 availability zones * 22 geographic regions * 1 local region ### Regions Regions provide physically separated availability zones, which are connected with low latency, high throughput, and highly redundant networking. ### Availability Zones Availability Zones offer high availability, fault tolerance and scalability. * Consists of one or more discrete data centers, each with redundant power, networking and connectivity, housed in separate facilities. * An availability zone is represented by a region code followed by a letter identifier, for example - `us-east-1a` * Local region is a single data center designated to compliment an existing AWS region * Edge locations are locations where end users access services located at AWS. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://notebook.iuriioapps.com/cloud/aws/high-availability/global-infrastructure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.