AWS Solution Architect Associate — Chapter 1
Kuch bhi start karne se pehle uski history ko samjhna bahut important hota hai. To pehle hum AWS ki history k baare me thoda sa jaan lete hain. Amazon ne apni pehli public service 2004 me launch ki thi , which was SQS. 2006 me dobara services launch ki gayi with SQS, S3, aur EC2 .
Aur aaj AWS har jagah hai. Bahut saari applications such as Dropbox, Netflix, Airbnb, or even the NASA, AWS ka use karti hain.
The first important concept in AWS are regions. Ab ye AWS region kya hai ? AWS region is nothing but a cluster of data centers. So many different data centers. Kai saare data centers milkar ek group banate hai, jinhe hum cluster keh sakte hain. Ye cluster worldwide hote hai aur yahi regions hote hai.
Jab bhi hum AWS services use karte hai , Har ek servie kisi specific region se linked hoti hai. That means that if we use a service in one region and we try to use it in another region, it will be like a new time of using the service.
Now, a question that may come up in your mind is, how do you choose an AWS region?
Isko samjhne k liye ek example lete hai. So let’s say , aap ek nayi application launch kar rahe ho. To aap service launch kahan karoge? Ho sakta hai aap America, India, or in Australia, koi bhi location schoose kar sakte ho, right ? Well, the answer is, of course it depends. But let’s look at some factors that may impact your choice of a AWS region.
The first one is compliance. Bole to application ka aur uska data ka scope kya hai . Agar hume ye chahiye ki data ka scope sirf country level par ho.
For example, India, data in India may have to stay in India and therefore you should launch your application in the India region.
The socnd one concept of latency. Agar aapke India se bolng karte hain then , it makes a lot of sense to deploy your application in India, close to your users. This will have a reduce latency. Ab agar hum wahi application Australia Or America me launch kar dete hain to data laod karne me latency badh jayegi, they will have a lot of lag at using your application.
And finally, pricing or Paisa. So, pricing does vary from region to region and you need to consult the applicant, the services, pricing.
Ek bahut important part hai AWS region ka, which is availability zones.
Each region will have many availability zones. Usually three, the minimum is two, and the max is six. But, really the usual is three.
So, let’s take the Sydney region as an example. The senior region code is ap-southeast-2. So, we can have two, have three availability zones in Sydney, ap-southeast-2a, ap-southeast-2b, and ap-southeast-2c.
Now, each of these availability zones are going to be one or more, just create data centers that will have redundant power, networking, and connectivity. That means that in southeast-2a, I can have two data centers maybe, as well two in 2b and two in 2c. But it could be one, it could be three, it could be four. We don’t really know. AWS doesn’t tell us that. But, what we know is that these availability zones are separate from each other so that they will be isolated from disasters. So, if something happens to ap-southeast-2a, we know that it is designed not to cascade into ap-southeast-2b, or ap-southeast-2c. So they’re really isolated from disasters. And then these data centers, these availability zones, they are connected with high bandwidth, ultra low latency networking and therefore altogether being linked together, it will form a region. Okay.
Next to, the only thing we need to know about AWS for the global infrastructure is the points of presence or edge locations, but you should know that AWS has more than 200 points of presence in 84 cities across 42 countries. And this will be very helpful when we deliver content to the end users with the lowest latency possible. Finally, to know if a service is available in your region, there is a region table you should check out right here.