After deciding to start learning AWS and cloud computing, I'm taking things one step at a time. Today, I'm exploring the basics of Amazon Web Services (AWS) and one of its important services: IAM (Identity and Access Management).
What is AWS?
Amazon Web Services (AWS) is a cloud computing platform that provides services developers and organisations can use to build, deploy, and manage applications without having to own and maintain all the underlying physical infrastructure themselves.
For example, instead of buying a physical server to host an application, a developer can use AWS services to run that application in the cloud. AWS offers many services for computing, storage, databases, networking, security, and more. As I continue learning, I want to understand not just how to build applications, but also how they run and operate in the cloud.
What is IAM?
IAM stands for Identity and Access Management. In simple terms, IAM helps control who can access AWS resources and what they are allowed to do. Imagine you're working on a project hosted on AWS. You might have different people working on the project, but not everyone needs access to every resource.
For example:
A developer might need permission to access certain application resources.
An administrator might need broader permissions to manage the AWS environment.
An application might need permission to access a specific storage service.
IAM helps you manage these identities and permissions.
Understanding the basic IAM components
As a beginner, these are the key concepts I'm learning:
- IAM users
An IAM user represents an identity that can have credentials and permissions in an AWS account. Users may be created for specific people or use cases, although AWS recommends federation and temporary credentials for many human and workload access scenarios.
- IAM groups
A group is a collection of IAM users. Instead of assigning the same permissions to multiple users individually, you can assign permissions to a group and manage them together.
- IAM roles
A role is an identity with a set of permissions that can be assumed by an authorised user, application, or AWS service. Roles are especially useful when temporary credentials are needed.
- IAM policies
Policies are documents that define permissions. They specify which actions are allowed or denied, and can also specify the resources those actions apply to.
For example, a policy could allow an identity to read objects from a particular Amazon S3 bucket without granting access to every bucket in the account.
Why is IAM important?
One of the biggest lessons I'm taking from this topic is that security is an important part of cloud computing. Giving everyone full access to an AWS account is not a good approach. People and applications should receive only the permissions they need to do their jobs. This principle is called least privilege.
I'm learning that understanding cloud computing isn't just about getting applications running. It's also about making sure resources are accessed securely and responsibly.
I'm still at the beginning of my AWS journey, so there's a lot more to explore. My next step is to get hands on experience with IAM by learning how to examine policies, understand permissions, and see how users and roles differ in practice.
This is one more step toward becoming a better developer and building a stronger foundation in cloud computing.
If you're also learning AWS, I'd love to hear about your journey and any advice you have for someone just getting started!
One step, one concept, one day at a time.
