INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

Core lesson 1 of 18Topic: AWS foundations

What is AWS? IAM, S3 and VPC explained for beginners

AWS (Amazon Web Services) is Amazon’s cloud platform. It provides services for servers, data storage, networking and more. This introductory lesson focuses on IAM for permissions, S3 for storage, and VPC for networking. Follow one internal reporting app to distinguish their roles.

Compare three service roles

An internal reporting app

AWS IAM

Permissions

Manage what people and apps may do

Manage who may do what in AWS. Authentication establishes who is making a request; authorization determines whether an operation is permitted.

In the reporting app

Permit the internal app to read the report.

Amazon S3

Storage

Store files and other data

Store data, such as a file, as an object. A bucket is the container that holds objects.

In the reporting app

Store the monthly-report PDF in a bucket.

Amazon VPC

Networking

Define the app’s network

Define a logically isolated network in AWS. Decide where the application runs and which paths its traffic uses.

In the reporting app

Provide the app’s network and its traffic paths.

What you will learn

Distinguish IAM, S3 and VPC, and explain how they support an internal reporting app.

Prerequisite

No prior AWS knowledge or account is required. Technical terms are explained on this page.

Recognize the three services by their roles

Reading a monthly report involves three separate jobs: permitting an operation, storing the data, and providing a network path. Use these roles to distinguish IAM, S3 and VPC.

Worked example: read a monthly report in an internal app

An employee opens a monthly-report PDF in an internal app. S3 stores the PDF. The app runs on EC2, an AWS virtual server, in a network defined with VPC. IAM manages the app’s AWS identity and permissions for the read.

How the reporting app reads a reportA conceptual teaching example
Employee, application in a VPC, and S31: an employee selects a PDF. 2: the internal app on EC2 in a VPC requests the PDF from 3: S3, shown outside the VPC. The dashed boundary marks the VPC. IAM permissions for the app are shown below as a separate check, not a network hop.VPC1EmployeeChoose a PDF2Internal appEC23Amazon S3PDF storageIAM: permissionsMay the app read the PDF?Employee, application in a VPC, and S31: an employee selects a PDF. 2: the internal app on EC2 in a VPC requests the PDF from 3: S3, shown outside the VPC. The dashed boundary marks the VPC. IAM permissions for the app are shown below as a separate check, not a network hop.VPC1EmployeeChoose a PDF2Internal appEC23Amazon S3PDF storageIAM: permissionsMay the app read the PDF?

Arrows show read requests; the dashed boundary marks the VPC. IAM permissions are checked separately from the network path.

  1. 1
    The employee chooses a report

    The employee signs in to the app and selects a PDF. Signing in to the app is distinct from authenticating the app’s AWS request.

  2. 2
    The app requests the PDF from S3

    The app uses its configured network path and AWS identity and permissions. A path alone, or permission alone, does not guarantee a successful read.

  3. 3
    Read the stored PDF

    The PDF is stored as an S3 object. When the required access conditions are met, the app retrieves it and displays it to the employee.

S3 is shown outside the VPC boundary. Arrows indicate read requests; this teaching diagram omits actual connection settings.
  1. Storage: which bucket holds which PDF?
  2. Permissions: which app may read which report?
  3. Networking: which path carries the app’s request to S3?
  4. Operations: who may see it, how long is it retained, and how is it removed?

Choosing a service still leaves decisions to you

Even when AWS operates the infrastructure and service, customers still decide what to store, who may act, and which configuration to use. This division is the shared responsibility model. The customer’s responsibilities vary by service; EC2 and S3 do not leave the same tasks to the customer.

Four decisions for the reporting app
DecisionWhat to check
AudienceWhich employees may read it? Is public access needed?
PermissionsIs reading enough, or are changes and deletion also permitted?
ConnectivityWhere does the app run, and how does it reach S3?
Operations and costHow long is data retained, costs checked, and unused data removed?

Three distinctions to keep clear

Separate what worked from what remains unchecked
AssumptionThe distinction
I can sign in, so I can do anything.Authentication identifies who is making the request. Authorization determines what is permitted. Signing in does not grant every operation.
It is stored in S3, so anyone can read it.Storage location and read permissions are separate. Check which data may be read, by whom, and under which conditions.
Creating a VPC sets the app’s permissions.Network paths and AWS permissions are separate. Creating a network does not grant permission to read the report.

Choose the service for each job

Choose an option to see the result and explanation.

Which service stores the monthly-report PDF?
Read the answer and reason

Answer: S3 · S3 stores the data. Here the PDF is an object stored in a bucket.

Which service manages the app’s permission to read the report?
Read the answer and reason

Answer: IAM · IAM manages identities and permissions. Decide not only which report is read, but which identity is permitted to read it.

Which service defines the app’s network and traffic paths?
Read the answer and reason

Answer: VPC · VPC defines the network. Design connectivity separately from data storage and permission to act.

Next: read, try, and explain

Once the three roles are clear, continue through IAM → S3 → VPC, pairing lessons with exercises. Change one condition and explain why the result changes. No AWS account or real credentials are needed.

  1. IAM: read policies, the rules that define who may do what.
  2. S3: distinguish storage from the conditions for saving and retrieving data.
  3. VPC: inspect routing, which directs traffic, and controls that permit or block it.
  4. Before using real resources, review account protection, costs, budget alerts and cleanup.

Common questions

Do I need an AWS account to start?

No account is needed for this lesson or the browser exercises. Before using real resources, establish the responsible administrator, identity setup and cost conditions.

Do IAM, S3 and VPC cover all of AWS?

They cover only part of AWS. Start by separating permissions, data storage and networking. Study EC2 for running apps, databases, observability and other services as needed.

Does an exercise result verify a real AWS configuration?

Exercises are bounded teaching models. Real environments can contain policies and architectural conditions outside their scope, so their outputs do not verify live permissions or connectivity.

Check, then explain in your own words

  1. Read the action/resource pair in IAM.
  2. Separate saving an S3 policy from reading an object.
  3. Trace forward and return conditions in VPC.
Check your understanding: Does storing a report in S3 establish who may read it?

Storage location and read permissions are separate decisions.

Check what is stored, which identity may perform which operation, and which network path is used. Selecting services and deciding how to use them are separate tasks.

Sources and conditions checked

The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.