What is AWS? A Simple Guide to Amazon Web Services for Beginners

2. The shared responsibility model

Security is a team job between you and AWS. AWS protects the cloud itself: buildings, hardware and the network. You protect what you put in the cloud: your data, your user permissions, your app settings, and, on a virtual server, the operating system updates.

Example: AWS guards the building like a society security guard. But if you leave your own flat door open, that is your responsibility. Interviewers love this question, so learn the phrase: AWS handles security of the cloud, you handle security in the cloud.

3. IAM: who can do what

IAM stands for Identity and Access Management. It controls who can log in and what they are allowed to do. Key ideas are users, groups, roles and policies. A policy is a JSON document that allows or denies actions.

Golden rules: do not use the root account (the email you signed up with) for daily work. Turn on MFA (multi-factor authentication). Give each person only the permissions they need. This is called least privilege. For apps running on AWS, use roles, which give short-lived credentials, instead of saving secret keys in code.

4. EC2: virtual servers

Amazon EC2 gives you virtual machines in the cloud, called instances. You pick the operating system, the size (CPU and memory) and the storage. A security group acts like a firewall that decides which traffic can reach your instance.

Example: a college project website can run on one small Linux instance. On EC2, you are responsible for patching the operating system yourself.

5. S3: storage for files

Amazon S3 stores files, called objects, inside containers called buckets. Each object has a key, which is like its full file name. You cannot change a bucket's name or Region after you create it.

Example: store student photos, PDFs or website backups in S3. New buckets are private by default, and Block Public Access is on. Keep it that way unless you truly need public files. Many real data leaks happened because someone made a bucket public by mistake.

6. Lambda and serverless

AWS Lambda runs your code without you managing any server. You write a small function, connect it to a trigger, and AWS runs it when needed. You pay for the number of requests and the time your code runs. One run of a Lambda function can last at most 15 minutes.

Example: when a student uploads a photo to S3, a Lambda function can automatically make a small thumbnail. No server sits idle waiting.

7. VPC: your private network

A VPC (Virtual Private Cloud) is your own private network inside AWS. You divide it into subnets. A public subnet can be reached from the internet, for example for a web server. A private subnet is hidden, which is good for a database.

Example: think of a VPC as a gated housing society. The main gate is the internet gateway. Visitors can reach the clubhouse (public subnet), but not the private flats (private subnet).

8. Pricing, Free Tier and budgets

AWS mostly charges pay-as-you-go: per hour, per second, per GB or per request. At the time of writing, new customers can choose a Free plan that comes with up to 200 US dollars in credits for six months, and more than 30 services have always-free monthly limits. These offers change, so always read the official Free Tier page before you start.

Use AWS Budgets to set a monthly limit and get email alerts when your actual or forecast cost crosses it. Note that alerts can arrive a little late, because billing data is updated only a few times a day.

How to get started

1. Create an AWS account and read the Free Tier terms carefully.
2. Turn on MFA for the root user, then stop using root for daily work.
3. Create a budget with an email alert at a small amount, such as 5 US dollars.
4. Pick the Mumbai Region (ap-south-1) in the console so your resources are close to you.
5. Explore with the web console first. Later, try the AWS CLI version 2 or AWS CloudShell, which runs in your browser.

Once the CLI is set up, a simple command like this lists your S3 buckets: aws s3 ls

And this shows which identity you are using, which is great for checking your setup: aws sts get-caller-identity

Common beginner mistakes

• Using the root account for everything and skipping MFA.
• Putting access keys inside code and pushing them to GitHub, where leaked keys can be found and misused quickly.
• Forgetting to stop or delete resources after practice, and then getting a surprise bill.
• Making an S3 bucket public just to make an error go away.
• Opening every port to the whole internet in a security group.
• Working in the wrong Region and thinking your resources have disappeared.
• Trying to learn 200 services at once instead of mastering the core few.

A simple learning roadmap

1. Learn cloud basics: what cloud is, pay-as-you-go, Regions and AZs, and the shared responsibility model.
2. Learn IAM well: users, groups, roles, policies, MFA and least privilege.
3. Launch an EC2 instance, connect to it, then terminate it.
4. Create an S3 bucket, upload files, and read about bucket policies and versioning.
5. Understand a VPC with public and private subnets and security groups.
6. Try a managed database such as Amazon RDS, and learn when to use DynamoDB.
7. Write a small Lambda function triggered by an S3 upload.
8. Learn monitoring basics with CloudWatch and cost control with Budgets.
9. Build one small project, like a static website on S3 or a simple API, and put it on your resume.
10. Prepare for the AWS Certified Cloud Practitioner exam as a first certificate if it fits your goals.

Conclusion

AWS looks huge, but the core is small: Regions, shared responsibility, IAM, EC2, S3, Lambda, VPC and cost control. Learn these well, practise with small hands-on tasks, and always watch your bill. With steady practice for a few weeks, you can speak about AWS with confidence in interviews.

Test what you have learned with short quizzes. Regular practice is the fastest way to make these ideas stick.

Browse practice quizzes

Sources

• Amazon Web Services, What is AWS: https://aws.amazon.com/what-is-aws/
• AWS Whitepaper, What is cloud computing: https://docs.aws.amazon.com/whitepapers/latest/aws-overview/what-is-cloud-computing.html
• AWS Whitepaper, Global infrastructure: https://docs.aws.amazon.com/whitepapers/latest/aws-overview/global-infrastructure.html
• AWS Documentation, AWS Regions: https://docs.aws.amazon.com/global-infrastructure/latest/regions/aws-regions.html
• AWS Well-Architected Framework, The pillars of the framework: https://docs.aws.amazon.com/wellarchitected/latest/framework/the-pillars-of-the-framework.html
• AWS Well-Architected Security Pillar, Shared responsibility: https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/shared-responsibility.html
• AWS IAM User Guide, Security best practices in IAM: https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html
• Amazon S3 User Guide, What is Amazon S3: https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html
• AWS Lambda Developer Guide, What is AWS Lambda: https://docs.aws.amazon.com/lambda/latest/dg/welcome.html
• AWS Free Tier: https://aws.amazon.com/free/
• AWS Cost Management User Guide, Managing your costs with AWS Budgets: https://docs.aws.amazon.com/cost-management/latest/userguide/budgets-managing-costs.html
• AWS CLI User Guide, Getting started: https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html
• AWS Certified Cloud Practitioner: https://aws.amazon.com/certification/certified-cloud-practitioner/