Topic lessonTopic: AWS foundations
AWS service map: compute, storage, networking and access
This AWS (Amazon Web Services) entry lesson helps you read services from the work they perform. Separate processing, retained data, connectivity and permission, then distinguish files from a database (DB) using inspection reports. It does not choose an architecture automatically or create real AWS resources.
Break a workload into four questions, explain representative service roles, and identify the next data, permission and connectivity checks.
It helps to distinguish shared infrastructure from customer configuration in What is cloud computing? Terms are explained here. No AWS account, credentials or real resources are required.
Read the job and the data before naming services
Consider a way for staff to retrieve equipment-inspection reports. Retrieving a completed PDF differs from filtering records by equipment ID, inspection date and team. Start with one sentence describing the input, processing, retained data and users.
| Name and abbreviation | Role in this lesson | What the name does not decide |
|---|---|---|
| Amazon EC2 (Elastic Compute Cloud) | A candidate for running application processing on a virtual-server instance in this example. | The required processing, durable data location or correctness of the result. |
| Amazon S3 (Simple Storage Service) | A candidate for storing and retrieving report PDFs as objects in a bucket. | Who may perform which operations, public access or retention. |
| Amazon RDS (Relational Database Service) | A candidate for relational records, such as equipment IDs and dates, in tables of a chosen database. | Queries, updates, data structure or compatibility with the chosen DB engine. |
| Amazon VPC (Virtual Private Cloud) | Configure a virtual network, routes and related connectivity conditions. | AWS operation permissions or correct application processing. |
| AWS IAM (Identity and Access Management) | Manage authentication and authorization for requests to AWS. | Network paths, application sign-in or database-user permissions. |
Map the purpose to four questions
- Use inspection reports → Check computeThe required processing leads to compute requirements and candidates.
- Use inspection reports → Check storageWhat is retained and how it is used determine the data questions.
- Use inspection reports → Check networkingWhere requests originate leads to connectivity questions.
- Use inspection reports → Check accessThe requesting identity and operation lead to permission questions.
- Use inspection reports
- State the processing, retained data and users first.
- Check compute
- Does application processing need a place to run? EC2 is one candidate.
- Check storage
- Distinguish S3 for the PDF from RDS for relational records.
- Check networking
- Review placement and connectivity. VPC routes and access permissions are separate questions.
- Check access
- Use IAM to reason about who requests which AWS operation.
This is not a deployment diagram. Do not read an S3 bucket as a resource placed in a VPC subnet. When accessing S3 from a VPC, review both the connectivity method and the permissions applying to the request. Providing a route does not itself grant permission to read an object.
Worked example: a changed requirement changes the next question
These are fictional inspection-work scenarios, not an automatic service selector. First review an existing application or approved storage location if it meets the requirements. The example does not assume creating EC2, S3, RDS and VPC for every case.
| Requirement | First distinction | Candidate to investigate | Still undecided |
|---|---|---|---|
| Retrieve a completed PDF by a known name. | Storing and retrieving the file itself. | S3 objects and keys. A key identifies an object within a bucket. | Retention and the requesting identity. This alone does not require RDS. |
| Filter by equipment ID, date and team, then update document records. | Separate the PDF from relational records used for queries and updates. | Tables and query requirements in a relational DB such as RDS. A DB engine is the software that processes database operations. | Whether an existing DB fits its structure and feature needs. Consider the PDF location separately. |
| Add aggregation in a custom application. | Separate retaining data from executing processing. | Compute candidates such as EC2, including whether the existing app can do the work. | This does not establish that EC2 is the best choice. Continue from the EC2 lesson to execution-model comparisons. |
| Let another business app read an existing PDF. | Separate the new requesting identity from its connectivity. | Check the IAM principal (the requesting identity), operation and resource; investigate VPC-related connectivity separately. | Stored data or a successful read by the original app does not establish success for the new request. |
Do not equate permission to create or modify an RDS resource through IAM with the authentication and permissions needed to sign in to a database and read a table. Distinguish application sign-in, AWS requests and database connections. This lesson asks for no real credentials.
Keep each observation within its scope
| What is known | Keep this check separate |
|---|---|
| The EC2 instance is running. | Does the intended processing work and retain the required data? |
| A PDF is stored in S3. | May the intended identity read that object? Storage is not authorization for public access. |
| A VPC route is configured. | Other connectivity conditions and AWS operation permissions still need checking. A route is not an IAM grant. |
| RDS has been selected. | Does the data structure, query behavior and database access meet requirements? Managed operation does not finish application design. |
Choose the next question after a condition changes
Choose an option to see the result and explanation.
Continue to IAM, then deepen the role you need
You do not need to memorize a service catalog. Continue with IAM’s identity, operation and resource, then follow the existing IAM → S3 → VPC path. Use the existing lessons below when you need execution-model or database-responsibility detail.
Existing lessons by question. IAM is the next foundation step; the other links are references as needed.
- Next foundation: identify the AWS principal, operation and resource:IAM authentication and permissions →
- Understand storage units for the PDF:S3 buckets, keys and objects →
- Review placement and network basics:VPCs, subnets and interfaces →
- Review responsibilities for a database:RDS operations and customer decisions →
- Deepen the four-role application example when selecting compute:Execution, storage, database and networking in the EC2 lesson →
- Revisit shared infrastructure and customer configuration:What is cloud computing? →
Check, then explain in your own words
- Describe the input, processing, retained data and users in one sentence.
- Separate compute, storage, networking and access; distinguish the PDF from relational records.
- Separate requirements already met by existing resources from genuine gaps.
- Change one condition and explain why the next question changes.
- Continue to IAM’s principal, operation and resource in the existing learning path.
Check your understanding: Does creating EC2, S3, RDS and VPC determine how a report workflow should work?
No. First separate the processing, retained data, connectivity and access requirements.
The PDF and relational records for queries and updates are different. Existing resources may be sufficient; collecting service names does not establish permissions or connectivity.
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.
- AWS overviewChecked:
Scope and conditionsService roles; not a service availability or pricing guarantee
Used in this lessonLesson overview and review
- What is Amazon EC2?Checked:
Scope and conditionsEC2 instances are virtual servers. Architecture and operating-system responsibilities depend on the chosen configuration.
Used in this lessonRead the job and the data before naming services Worked example: a changed requirement changes the next question Keep each observation within its scope Choose the next question after a condition changes
- Amazon S3: What is S3?Checked:
Scope and conditionsObject/API access and storage-class distinctions. Documentation review, not live AWS verification.
Used in this lessonRead the job and the data before naming services Worked example: a changed requirement changes the next question Keep each observation within its scope Choose the next question after a condition changes
- What is Amazon RDS?Checked:
Scope and conditionsManaged RDS responsibilities versus customer design, not identical features for all engines.
Used in this lessonRead the job and the data before naming services Worked example: a changed requirement changes the next question Keep each observation within its scope Choose the next question after a condition changes
- What is Amazon VPC?Checked:
Scope and conditionsVirtual networking; no implicit Internet reachability
Used in this lessonRead the job and the data before naming services Map the purpose to four questions Worked example: a changed requirement changes the next question Keep each observation within its scope Choose the next question after a condition changes
- What is IAM?Checked:
Scope and conditionsIdentity and access concepts
Used in this lessonRead the job and the data before naming services Map the purpose to four questions Worked example: a changed requirement changes the next question Keep each observation within its scope Choose the next question after a condition changes
- Gateway endpoints for Amazon S3Checked:
Scope and conditionsSame-Region routes, no extension through peering/VPN/TGW/Direct Connect, service permissions and S3 private-DNS inbound-Resolver-only split behavior.
Used in this lessonMap the purpose to four questions Keep each observation within its scope
- S3 Block Public AccessChecked:
Scope and conditionsFour controls, applicable levels and most restrictive combination
Used in this lessonKeep each observation within its scope
- Security in Amazon RDSChecked:
Scope and conditionsDistinguish IAM permissions for RDS resource management, database authentication/access, and network controls. A short boundary explanation, not a security configuration runbook.
Used in this lessonRead the job and the data before naming services Worked example: a changed requirement changes the next question Keep each observation within its scope