In this video, Jeff Winesett describes the geographical and physical isolation provided by AWS in regions and availability zones. AWS regions and availability zones are used to achieve high availability, high redundancy and disaster recovery requirements.
- [Narrator] EC2 instances can be launched in one or more geographical regions. Each region is a geographically independent collection of AWS resources. AWS currently operates in 16 geographic regions around the world with more coming online all the time. These regions are distributed worldwide within five primary land areas: North America, South America, Europe, Asia, and Australia.
There are six regions in North America: US East, located in Virginia, US East, located in Ohio, US West, located in Northern California, US West, located in Oregon, one in Central Canada, and a region called Gov Cloud. The Gov Cloud region is designed to allow US government agencies, contractors, and their customers, to move highly sensitive data into the cloud by addressing their specific regulatory and compliance requirements.
There are three regions located in Europe: Ireland, London, and Frankfurt. And there is one located in South America, which is in San Paulo. And there are six regions in the Asia Pacific area: one in Singapore, and one in Sydney, and one in Tokyo, one in Beijing, one in Mumbai, and one in Seoul. AWS customers choose the region into which to launch their services.
Regions are independent of one another, and there is no data replication between them. The customer can decide to launch services in more than one region. Regions can help with very strict high availability and disaster recovery requirements that specify the need for redundant systems located very far apart geographically. While it's great to know that building a system spanning two regions is an option, most system requirements can be met while working within a single region.
Even within a region, geographical isolation can be achieved to meet high availability and disaster recovery needs. This is because each region consists of multiple locations called availability zones. Availability zones are distinct locations that are engineered to be insulated from failures from other availability zones. And provide inexpensive, low-latency network connectivity to other availability zones in the same region. Think of these as distinct data centers that are connected by a fast fiber network.
Just within North America, there are six regions available, and each of these regions consists of multiple availability zones. Looking at just US East Virginia region, which is the oldest of the regions, it has five availability zones, more than any other region. The rest has either two or three. Every region has at least two availability zones. Each of these availability zones are connected by a fast fiber network connection, and each are physically isolated from each other.
A local disaster, such as a fire, flood, tornado or other physical breach occurring in one availability zone, will not affect the other zones. So using multiple availability zones within a region provides an excellent option for meeting high availability and disaster recovery needs. Designed for Failure: Lesson #2 Utilize multiple availability zones and even multiple regions if required. Availability zones are conceptually like logical data centers.
Deploying system and application architecture to multiple availability zones ensures high availability and ease of disaster recovery.
- Benefits of cloud services
- Making architectures scalable
- Examining cloud constraints
- Virtual servers, EC2, and Elastic IP
- Using the Amazon machine image
- Elastic load balancing
- Using CloudWatch for monitoring
- Security Models
- Elastic block storage
- S3, CloudFront, and Elastic Beanstalk
- Handling queues, workflows, and notifications
- Caching options and services
- Identity and access management
- Creating a custom server image
- Application deployment strategies
- Serverless architectures