[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"cheat-sheet---en":3,"domain-info---en":3,"topic-info----en":3,"lesson-aws-certified-cloud-practitioner-cloud-technology-and-services-global-infrastructure-edge-locations-and-cloudfront-en":4,"prev-aws-certified-cloud-practitioner-cloud-technology-and-services-global-infrastructure-edge-locations-and-cloudfront-en":19,"next-aws-certified-cloud-practitioner-cloud-technology-and-services-global-infrastructure-edge-locations-and-cloudfront-en":288},null,{"locked":5,"reason":6,"meta":7,"item":3},true,"paywall",{"title":8,"description":9,"isFree":10,"estimatedMinutes":11,"difficulty":12,"learningObjectives":13},"Edge Locations and Amazon CloudFront","Learn what edge locations are, how Amazon CloudFront uses them as a content delivery network to serve content close to users, and the performance, security, and cost benefits this brings.",false,15,"beginner",[14,15,16,17,18],"Define an edge location and explain how it differs from a Region","Explain what a content delivery network (CDN) is and what Amazon CloudFront does","Describe how CloudFront serves a request, including cache hits and origin fetches","Explain the role of regional edge caches","Identify the performance, security, and cost benefits of CloudFront",{"locked":10,"reason":3,"meta":20,"item":30},{"title":21,"description":22,"isFree":5,"estimatedMinutes":23,"difficulty":12,"learningObjectives":24},"AWS Regions and Availability Zones","Learn how AWS organizes its global infrastructure into Regions and Availability Zones, and the four factors that decide which Region you should run a workload in.",16,[25,26,27,28,29],"Define an AWS Region and an Availability Zone","Explain why each Region has at least three physically separate Availability Zones","Describe how Availability Zones are isolated yet connected with low-latency networking","Identify the four factors for choosing a Region: compliance, latency, pricing, and service availability","Explain why most AWS resources are scoped to a single Region",{"id":31,"title":21,"body":32,"description":22,"difficulty":12,"estimatedMinutes":23,"extension":223,"infographics":224,"isFree":5,"learningObjectives":234,"meta":235,"navigation":5,"path":236,"quiz":237,"seo":285,"stem":286,"__hash__":287},"courses/courses/aws-certified-cloud-practitioner/en/domains/03-cloud-technology-and-services/02-global-infrastructure/01-regions-and-availability-zones.md",{"type":33,"value":34,"toc":212},"minimark",[35,40,44,47,52,56,72,75,79,82,85,103,107,110,162,165,169,172,185,188,192],[36,37,39],"h2",{"id":38},"why-this-matters","Why this matters",[41,42,43],"p",{},"Every resource you launch in AWS runs somewhere physical. AWS organizes all of that hardware into a global structure of Regions and Availability Zones, and almost every service decision starts with picking the right one. The exam tests this directly, and in real work the choice affects your latency, your costs, and whether you meet the law.",[41,45,46],{},"The structure is simple once you see the layers: the world is divided into Regions, each Region holds several Availability Zones, and each Availability Zone is built from one or more data centers.",[48,49],"infographic",{"alt":50,"slug":51},"A diagram showing the AWS global infrastructure as nested layers: the world divided into Regions, each Region containing at least three Availability Zones, and each Availability Zone made of one or more data centers.","regions-and-azs-hierarchy",[36,53,55],{"id":54},"what-is-a-region","What is a Region",[41,57,58,59,63,64,67,68,71],{},"An AWS Region is a physical location in the world where AWS clusters its data centers. Examples include US East (Ohio), Europe (Ireland), and Asia Pacific (Sydney). Each Region has a code you will see throughout AWS, such as ",[60,61,62],"code",{},"us-east-2",", ",[60,65,66],{},"eu-west-1",", or ",[60,69,70],{},"ap-southeast-2",".",[41,73,74],{},"Regions are isolated from one another by design. Resources you create in one Region are not automatically copied to another, and traffic stays within a Region unless you explicitly move it. This isolation is a feature: a problem in one Region does not spill into the others. It also means you choose a Region on purpose for each workload, rather than getting a single global pool of resources.",[36,76,78],{"id":77},"what-is-an-availability-zone","What is an Availability Zone",[41,80,81],{},"An Availability Zone (AZ) is one or more discrete data centers within a Region, each with its own redundant power, networking, and connectivity, housed in separate facilities. Each Region has at least three Availability Zones.",[41,83,84],{},"The zones in a Region are far enough apart that a single fire, flood, or power outage is unlikely to hit more than one of them. At the same time, they are close enough to be linked by high-bandwidth, low-latency, dedicated fiber, so data moves between them quickly. All traffic between Availability Zones is encrypted. This combination, separate enough to fail independently but connected enough to work together, is the foundation of high availability on AWS.",[41,86,87,88,63,91,94,95,98,99,102],{},"AZ codes are the Region code plus a letter, like ",[60,89,90],{},"us-east-2a",[60,92,93],{},"us-east-2b",", and ",[60,96,97],{},"us-east-2c",". There is also a stable AZ ID, such as ",[60,100,101],{},"use2-az1",", that points to the same physical zone in every account, which is useful when you need to line up zones across accounts.",[36,104,106],{"id":105},"choosing-the-right-region","Choosing the right Region",[41,108,109],{},"You are not meant to spread a workload across every Region. You pick one (or a few) based on four main factors.",[111,112,113,126],"table",{},[114,115,116],"thead",{},[117,118,119,123],"tr",{},[120,121,122],"th",{},"Factor",[120,124,125],{},"Question it answers",[127,128,129,138,146,154],"tbody",{},[117,130,131,135],{},[132,133,134],"td",{},"Compliance",[132,136,137],{},"Does a law require the data to stay in a specific country or area?",[117,139,140,143],{},[132,141,142],{},"Latency",[132,144,145],{},"Which Region is closest to your users, for the fastest response?",[117,147,148,151],{},[132,149,150],{},"Pricing",[132,152,153],{},"Service prices differ by Region. Which fits your budget?",[117,155,156,159],{},[132,157,158],{},"Service availability",[132,160,161],{},"Are the services and features you need offered in that Region?",[41,163,164],{},"Compliance usually wins when it applies. If a data residency law says customer data must stay inside a country, you choose a Region in that country first, then weigh the rest. After that, latency and proximity to your users drive a better experience, pricing varies because the same service can cost more in one Region than another, and service availability matters because not every service launches in every Region at the same time.",[36,166,168],{"id":167},"region-versus-availability-zone-in-practice","Region versus Availability Zone in practice",[41,170,171],{},"Most AWS services are Regional or zonal, so it helps to know which scope you are working in.",[173,174,175,179,182],"ul",{},[176,177,178],"li",{},"You launch an EC2 instance into a specific Availability Zone.",[176,180,181],{},"You create an Amazon S3 bucket in a Region, and S3 spreads the data across zones for you.",[176,183,184],{},"To survive the loss of one data center, you run across multiple Availability Zones in the same Region. This is the Multi-AZ pattern, covered later in this topic.",[41,186,187],{},"A few services are global rather than Regional, such as IAM and Amazon Route 53, but those are the exception. The default mental model is: a Region holds zones, and you place resources into zones inside the Region you chose.",[36,189,191],{"id":190},"exam-tips","Exam tips",[173,193,194,197,200,203,206,209],{},[176,195,196],{},"An AWS Region is a physical location that contains multiple Availability Zones; Regions are isolated from each other.",[176,198,199],{},"Each Region has at least 3 Availability Zones.",[176,201,202],{},"An Availability Zone is one or more discrete data centers with redundant power and networking, physically separated but linked by low-latency, encrypted, high-bandwidth fiber.",[176,204,205],{},"Choose a Region using 4 factors: compliance (data residency), latency (proximity to users), pricing (varies by Region), and service availability (not every service is in every Region).",[176,207,208],{},"Compliance and data residency requirements override the other factors when they apply.",[176,210,211],{},"Running across multiple Availability Zones in a Region is how you build for high availability.",{"title":213,"searchDepth":214,"depth":214,"links":215},"",3,[216,218,219,220,221,222],{"id":38,"depth":217,"text":39},2,{"id":54,"depth":217,"text":55},{"id":77,"depth":217,"text":78},{"id":105,"depth":217,"text":106},{"id":167,"depth":217,"text":168},{"id":190,"depth":217,"text":191},"md",[225],{"slug":51,"concept":226,"style":227,"aspectRatio":228,"labels":229},"Nested containment: a Region box labeled us-east-1 holds at least three Availability Zone boxes, and one zone labeled us-east-1a opens up to show it is built from one or more data centers. Thin fiber lines link the zones, noted as encrypted and low latency. The Availability Zone layer gets the orange accent, because the zone is the unit you place resources into. The takeaway: a Region holds at least three isolated zones and each zone is one or more data centers, which is the structure high availability is built on.","diagram","16:9",[230,231,232,233],"Region: isolated location (us-east-1)","At least 3 AZs per Region","AZ: 1+ data centers (us-east-1a)","Zones linked by encrypted low-latency fiber",[25,26,27,28,29],{},"/courses/aws-certified-cloud-practitioner/en/domains/03-cloud-technology-and-services/02-global-infrastructure/01-regions-and-availability-zones",{"passingScore":238,"questions":239},70,[240,249,257,261,271,277],{"question":241,"type":242,"options":243,"correctAnswer":245,"explanation":248},"What is an AWS Region?","single",[244,245,246,247],"A single data center owned by AWS","A physical location in the world that contains multiple Availability Zones","A global cache that stores copies of your content close to users","A billing boundary that groups your AWS accounts","An AWS Region is a physical geographic location, such as Ireland or Ohio, that holds a cluster of Availability Zones. A single data center is too small to be a Region, and caching content near users is the job of edge locations, not Regions.",{"question":250,"type":242,"options":251,"correctAnswer":254,"explanation":256},"How many Availability Zones does each AWS Region contain at a minimum?",[252,253,254,255],"One","Two","Three","Five","Each AWS Region is made up of at least three isolated, physically separate Availability Zones. This minimum lets you design highly available applications that survive the loss of one zone.",{"question":258,"type":242,"options":259,"correctAnswer":134,"explanation":260},"A healthcare company must keep all patient data inside its own country because of a data residency law. Which Region-selection factor takes priority here?",[134,142,150,158],"When a law dictates where data may physically live, compliance and data residency override the other factors. You must choose a Region in a country that satisfies the regulation, even if another Region would be cheaper or closer.",{"question":262,"type":263,"options":264,"correctAnswers":269,"explanation":270},"Which of the following are valid factors to weigh when choosing an AWS Region? (Select all that apply.)","multiple",[265,266,267,268],"Compliance and data residency requirements","Latency to your users","The price of services, which varies by Region","Whether the services you need are available in that Region",[265,266,267,268],"AWS pricing differs from one Region to another, not every service launches in every Region, latency depends on how close the Region is to your users, and compliance can force a specific location. All four shape the decision.",{"question":272,"type":242,"options":273,"correctAnswer":275,"explanation":276},"An Availability Zone is always a single, standalone data center.",[274,275],"True","False","An Availability Zone is one or more discrete data centers, each with redundant power, networking, and connectivity. Treating an AZ as exactly one building is a common misconception.",{"question":278,"type":242,"options":279,"correctAnswer":283,"explanation":284},"Why are the Availability Zones in a Region placed in physically separate locations?",[280,281,282,283],"To make each zone cheaper to operate","To give every zone its own Region code","To force all traffic between zones onto the public internet","So a single fire, flood, or power loss affects only one zone","Physical separation means a local disaster in one zone does not take down the others, which is what makes Multi-AZ designs fault tolerant. The zones are still linked by private, high-bandwidth, low-latency fiber, and that traffic is encrypted rather than sent over the public internet.",{"title":21,"description":22},"courses/aws-certified-cloud-practitioner/en/domains/03-cloud-technology-and-services/02-global-infrastructure/01-regions-and-availability-zones","TIUHr79AMlKu5IGM7q3m_C9HKmC0b3c6Fdt2DYQdEt4",{"locked":5,"reason":6,"meta":289,"item":3},{"title":290,"description":291,"isFree":10,"estimatedMinutes":23,"difficulty":292,"learningObjectives":293},"High Availability and Multi-Region Design","Learn how to use multiple Availability Zones and multiple Regions to keep applications running through failures, and how high availability differs from disaster recovery.","intermediate",[294,295,296,297,298],"Define high availability and explain why single points of failure are a risk","Explain how a Multi-AZ design protects against the loss of one data center","Describe when a multi-Region design is needed and what it protects against","Distinguish high availability from disaster recovery","Compare active-passive and active-active multi-Region patterns"]