Getting Started with AWS

When someone starts AWS for the first time, the biggest problem is not the services. The problem is the shape of AWS itself. You see EC2, S3, Lambda, RDS, DynamoDB, CloudFront, Route 53, IAM and many more names, and everything feels mixed together. So before learning individual services, it makes more sense to understand the base first.

This blog covers what AWS is, why people use it, how AWS grew, what the global infrastructure looks like, how Regions and Availability Zones work, what Edge Locations do, and why some services are global while most services stay inside a Region.

What AWS Is

AWS stands for Amazon Web Services. It is a cloud provider, which means it gives us computing power, storage, databases, networking, and many other services over the internet. Instead of buying physical servers and managing everything ourselves, we can use AWS on demand.

That is the main idea of cloud. If an application needs one server today and ten servers tomorrow, AWS makes that change possible without rebuilding the whole environment. If the application no longer needs those resources, we can stop or delete them. This flexibility is one of the biggest reasons cloud computing became so important.

AWS is also not only for huge companies. Small apps, personal projects, startups, and enterprise systems can all use the same platform. The difference is only in scale and architecture.

Why People Use AWS

AWS helps us build applications that can grow. That is why people use it for website hosting, mobile backends, enterprise IT, backup and storage, big data analytics, social apps, and gaming. The use cases are wide because AWS is not one product. It is a platform made of many services.

One project may use S3 and CloudFront for static files. Another may use EC2, RDS, and CloudWatch. A third may use Lambda, API Gateway, and DynamoDB. The pattern changes, but the idea stays the same: choose the services that fit the problem.

A Short AWS History

AWS did not start as the large platform we know today. It began internally in 2002. In 2003, Amazon recognized that its infrastructure was one of its core strengths, and the idea started moving toward a public service.

In 2004, AWS launched publicly with SQS. In 2006, AWS re-launched with SQS, S3, and EC2. In 2007, AWS launched in Europe. That history matters because it shows how AWS grew from basic building blocks into a full cloud ecosystem.

AWS Global Infrastructure

AWS is not one giant computer in one place. It is a global infrastructure made of Regions, Availability Zones, data centers, and Edge Locations, also called Points of Presence. This is the part that confuses many beginners, but once it is clear, the rest of AWS becomes much easier to follow.

The first thing to understand is this: when you create a resource in AWS, location matters. Some resources live inside a Region. Some are global. If you do not pay attention to that, you can create something in one place and then think it disappeared when you switch the console to another place.

What an AWS Region Is

An AWS Region is a physical location in the world where AWS has a cluster of data centers. Examples include us-east-1, eu-west-3, and ap-southeast-2. Each Region is separate from the others.

If you create an EC2 instance in us-east-1, that instance belongs to us-east-1. If you later switch the console to eu-west-3, you will not see that instance there. It is not gone. You are just looking in a different Region.

Most AWS services are Region scoped, which means the resource belongs to the Region you selected. EC2 is a simple example of this.

How to Choose a Region

Region choice should be practical, not random. The first thing to check is compliance. Some businesses have legal or data governance rules that require data to stay in a specific area. In those cases, the Region is not just a technical choice. It is also a policy choice.

The second thing is latency. If your users are in Europe, putting your app in a European Region usually gives better response times than placing it far away. Closer is usually faster.

The third thing is service availability. Not every AWS service or feature is available in every Region. Before you launch, check that the Region supports the services you need.

The fourth thing is pricing. AWS pricing can vary by Region, so two Regions that both fit your technical needs may still have different costs.

What an Availability Zone Is

An Availability Zone, or AZ, is an isolated location inside a Region. Each Region usually has three AZs, and AWS can have anywhere from three to six in a Region. For example, the Sydney Region ap-southeast-2 may have ap-southeast-2a, ap-southeast-2b, and ap-southeast-2c.

Each AZ is one or more discrete data centers with redundant power, networking, and connectivity. They are separated from each other so failures in one AZ do not automatically take down the others. At the same time, they are connected by high-bandwidth, low-latency networking.

That is why AZs matter for high availability. If you run an application in only one AZ and that AZ has a problem, the application can go down. If you spread the application across multiple AZs, you improve resilience.

Region: ap-southeast-2

Availability Zones:
- ap-southeast-2a
- ap-southeast-2b
- ap-southeast-2c

What Edge Locations Do

Edge Locations are AWS Points of Presence. Their job is to bring content closer to users so content loads with lower latency. AWS has hundreds of these locations across many cities and countries.

This matters most for content delivery. CloudFront uses Edge Locations to cache and serve files closer to the user. If your site has images, CSS, JavaScript, or video, a nearby Edge Location can reduce the delay that comes from fetching everything from one distant server.

Cache means a stored copy. Instead of every user hitting the same faraway origin server, CloudFront can serve repeated content from a location that is closer to the user.

Global Services and Region Scoped Services

Some AWS services are global. They are not tied to one specific Region in the same way EC2 is. Common global services include IAM, Route 53, CloudFront, and WAF.

IAM handles identity and access. Route 53 is DNS. CloudFront is the content delivery network. WAF is a web application firewall.

Most other AWS services are Region scoped. EC2, Elastic Beanstalk, Lambda, and Rekognition are examples. With these services, you need to pay attention to the selected Region because the resource exists there.

The Beginner Mistake That Happens a Lot

One of the most common beginner mistakes is thinking a resource was deleted when it was only created in another Region. For example, you create an EC2 instance in us-east-1, then later switch the console to eu-west-3 and cannot find it.

At that point, the right question is not "where did AWS put my instance?" The right question is "which Region am I looking at right now?" Most of the time, the answer is right there in the console selector.

This sounds small, but it saves a lot of confusion.

Best Practices

Start with the foundation before jumping into specific services. Learn what AWS is, what a Region is, what an Availability Zone is, what Edge Locations are, and which services are global. That makes later topics much easier to understand.

Choose your Region based on compliance, latency, service support, and cost. Do not pick a Region only because it is the default.

When availability matters, think in terms of multiple AZs. One AZ is simpler, but multiple AZs give you better fault tolerance.

Keep checking the Region selector in the AWS Console when you are creating, searching, or debugging resources. A lot of confusion disappears once that habit becomes automatic.

Summary

AWS is a cloud provider that gives us computing, storage, databases, networking, and many other services on demand. It started as a small internal idea and grew into a global cloud platform with many services for many kinds of applications.

The most important foundation is AWS global infrastructure. A Region is a physical location with a cluster of data centers. An Availability Zone is an isolated location inside a Region. Edge Locations help deliver content closer to users. Some services like IAM, Route 53, CloudFront, and WAF are global, while most services like EC2, Elastic Beanstalk, Lambda, and Rekognition are Region scoped.

Once this base is clear, the rest of AWS stops feeling like random service names and starts looking like a system you can actually use.