George has launched three EC2 instances inside the US-East-1a zone with his AWS account. Ray
has
launched two EC2 instances in the US-East-1a zone with his AWS account. Which of the below
entioned statements will help George and Ray understand the availability zone (AZ. concept
better?
A.
The instances of George and Ray will be running in the same data centre
B.
All the instances of George and Ray can communicate over a private IP with a minimal cost
C.
All the instances of George and Ray can communicate over a private IP without any cost
D.
The US-East-1a region of George and Ray can be different availability zones
Explanation:
Each AWS region has multiple, isolated locations known as Availability Zones. To ensure that the
AWS
resources are distributed across the Availability Zones for a region, AWS independently maps the
Availability Zones to identifiers for each account. In this case the Availability Zone US-East-1a
where George’s EC2 instances are running might not be the same location as the US-East-1a
zone of Ray’s EC2 instances. There is no way for the user to coordinate the Availability Zones
between accounts.
D
D
D But US-East-1a should be used to describe a region, not an AZ.
Agree with Flyboy
The answer is A.
US-East-1 is a region.
Within that region there are 4 availability zones: us-east-1a, us-east-1b, us-east-1c, us-east-1e.
They all but say it here:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html
Each region has multiple, isolated locations known as Availability Zones….Amazon operates state-of-the-art, highly-available data centers. Although rare, failures can occur that affect the availability of instances that are in the same location. If you host all your instances in a single location that is affected by such a failure, none of your instances would be available.
I’ve spoken with AWS reps who confirmed it.
Sorry, you’re wrong, in the doc. you quoted, it clearly said:
To ensure that resources are distributed across the Availability Zones for a region, we independently map Availability Zones to identifiers for each account. For example, your Availability Zone us-east-1a might not be the same location as us-east-1a for another account. There’s no way for you to coordinate Availability Zones between accounts.