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 3 of 18Topic: AWS foundations

On-premises vs AWS: infrastructure, operations and cost boundaries

On-premises and AWS differ in how resources are obtained and who manages each layer. Moving an application does not settle its data, access or operating responsibilities. Compare the same internal reporting application across equipment, OS, operations and cost, without assuming that cloud is always cheaper or fully managed.

What you will learn

Compare both options against the same requirements, identifying infrastructure responsibilities, retained operational work, cost components and migration checks.

Prerequisite

Know cloud service models and distinguish OS, application and data. This lesson does not purchase equipment, enter contracts or create AWS resources.

Compare management layers for the same application

From application to equipment: comparison with an EC2-based option
From application to equipment: comparison with an EC2-based option1: Common requirements — An on-premises arrangement may outsource work; examine its actual contracts. — On-premises option. 2: Common requirements — This branch uses EC2. A service such as S3 has a different management boundary. — EC2-based option12Common requirementsOn-premises optionEC2-based optionFrom application to equipment: comparison with an EC2-based option1: Common requirements — An on-premises arrangement may outsource work; examine its actual contracts. — On-premises option. 2: Common requirements — This branch uses EC2. A service such as S3 has a different management boundary. — EC2-based option12CommonrequirementsOn-premisesoptionEC2-basedoption
  1. Common requirements → On-premises optionAn on-premises arrangement may outsource work; examine its actual contracts.
  2. Common requirements → EC2-based optionThis branch uses EC2. A service such as S3 has a different management boundary.
Common requirements
Keep users, data, recovery needs and functionality comparable.
On-premises option
Review owned equipment, supplier contracts and operational staffing.
EC2-based option
AWS manages the infrastructure; the customer manages the guest OS and applications.

On-premises arrangements vary in location and outsourcing. AWS also offers different boundaries: an EC2 customer manages its guest OS, while other services abstract more of that work. “Inside or outside the office” is not enough to assign operational ownership.

Assign the work that remains after a move

Comparison using an EC2-based AWS option
AreaOn-premises checksEC2-based AWS checks
Facilities and equipmentOwnership, facility provider and maintenance contractsThe infrastructure boundary provided by AWS
Guest OS and applicationsUpdates, configuration and operating ownerCustomer-side updates, configuration and ownership
Data and accessAllowed users, operations, retention and recovery needsThe same needs, plus IAM and service-specific controls
Capacity and recoveryExpansion, maintenance, spare capacity and recovery processResource choice, limits, placement and recovery design

Compare complete costs over the same period

A comparison worksheet, not a price list
ComponentQuestions to include
Compute, storage and communicationCapacity, runtime, transfer destination, growth and fixed commitments
Equipment and contractsPurchase, facilities, maintenance, refresh, connectivity and existing obligations
OperationsOS/application maintenance, incidents and staffing
Migration and exitData movement, parallel running, tests, cutover and reversal conditions
Retained resourcesUnused resources, retained data and ongoing contractual charges

Being able to change capacity does not guarantee lower total cost. Use current terms for the selected AWS services, Regions and purchasing options, and actual on-premises contracts and operating effort. This lesson supplies no fixed savings percentage or price.

Worked example: reports peak at month end

A demand pattern alone does not settle deployment
ObservationInformation still needed
Processing peaks at month endScaling unit, runtime, data volume and transfer time
The app reads an internal systemConnectivity, latency, identity and whether the dependency can change
It stores internal documentsLocation, access, retention, deletion and recovery requirements
Equipment contracts remain activeParallel-running period, exit terms, renewal timing and migration cost

Choose an option to see the result and explanation.

EC2 compute appears cheaper. Does that establish a lower total migration cost?
Read the answer and reason

Answer: No: include storage, transfer, operations, migration and contracts · Compare complete solutions that meet the same requirements. Omitting non-compute charges, existing obligations or migration work can reverse the conclusion.

Make the decision from requirements and evidence

  1. Write common requirements for users, data, function and disruption tolerance.
  2. Identify what moves and which dependencies, equipment and contracts remain.
  3. Assign management, updates and recovery for each layer.
  4. Compare costs over the same period, including migration and exit.
  5. Define a small evaluation, cutover conditions and a reversal plan before committing.

Check, then explain in your own words

  1. Separate responsibility for infrastructure, guest OS, applications and data.
  2. Compare complete costs under the same requirements.
  3. Explain why a month-end peak alone does not settle the choice.
Check your understanding: Does moving to AWS always remove guest-OS patching work?

It depends on the service. EC2 guest-OS management remains with the customer.

Use the service’s actual management boundary rather than location. Then assign the customer-side work to a concrete owner within the organization.

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.