Amazon EC2 are hosted in multiple locations world wide. These locations are composed of Regions and Availability Zones.
* Regions –
A Geographical Area that scale the world. Each region is completely independent to each other. This is to achieve highest fault tolerance and stability.
1. Resources aren’t replicated across regions unless you do so specifically.
2. Data transfers between regions are chargeable.
* Availability Zone –
Physical Data center within a Region.
1. Each Regions has multiple (A minimum of 2) isolated locations known as Availability Zones. i.e. 2 or More Physical Data centers.
2. Each Availability Zone inside a region is isolated but connected through low-latency (Computer network that is optimized to process a very high volume of data messages with minimal delay) links.
* Edge Location –
Edge Locations are consumable locations for AWS Services.
You cannot place a resource in Edge location, however you can only consume services available in Edge Locations.
For Example :-
DNS Service (SLA – 100%).
* According to the AWS service, and specifically for EC2, each resource can belong to either whole AWS(global), Regions or Availability Zone.
For example :-
IAM is global, AMIs are regional and instances belong to AZs, and so on.
* Endpoints –
URLs acting as entry point for a web service often used to access a service, a region and/or an availability zones etc..
1. Endpoint aim is to further reduce data latency in your applications.
2. Most (Not all) Amazon Web Services offer a regional endpoint to make your requests. Though, not all the AWS services support endpoints.
For Example :-
IAM endpoint is https://iam.amazonaws.com. (IAM do not support regions; therefore, their endpoints do not include a region)
DynamoDB endpoint is https://dynamodb.eu-west-1.amazonaws.com. (Endpoint include a region)
* AWS documentation available below:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html
* Regions –
A Geographical Area that scale the world. Each region is completely independent to each other. This is to achieve highest fault tolerance and stability.
1. Resources aren’t replicated across regions unless you do so specifically.
2. Data transfers between regions are chargeable.
* Availability Zone –
Physical Data center within a Region.
1. Each Regions has multiple (A minimum of 2) isolated locations known as Availability Zones. i.e. 2 or More Physical Data centers.
2. Each Availability Zone inside a region is isolated but connected through low-latency (Computer network that is optimized to process a very high volume of data messages with minimal delay) links.
* Edge Location –
Edge Locations are consumable locations for AWS Services.
You cannot place a resource in Edge location, however you can only consume services available in Edge Locations.
For Example :-
DNS Service (SLA – 100%).
* According to the AWS service, and specifically for EC2, each resource can belong to either whole AWS(global), Regions or Availability Zone.
For example :-
IAM is global, AMIs are regional and instances belong to AZs, and so on.
* Endpoints –
URLs acting as entry point for a web service often used to access a service, a region and/or an availability zones etc..
1. Endpoint aim is to further reduce data latency in your applications.
2. Most (Not all) Amazon Web Services offer a regional endpoint to make your requests. Though, not all the AWS services support endpoints.
For Example :-
IAM endpoint is https://iam.amazonaws.com. (IAM do not support regions; therefore, their endpoints do not include a region)
DynamoDB endpoint is https://dynamodb.eu-west-1.amazonaws.com. (Endpoint include a region)
* AWS documentation available below:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html
Comments
Post a Comment