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

Esc to close · Search terms stay on your device

LEARNING日本語

Topic lessonTopic: RDS and SQL Server: management, connections and deployment

SQL Server on AWS: choosing RDS, RDS Custom or EC2

Choose a SQL Server deployment from the required operations and the management work you can own. Compare ordinary RDS, RDS Custom and EC2 for the same document application, covering host access, maintenance, availability, recovery, licensing and cost as well as features.

What you will learn

Compare three deployments under matched requirements and explain ordinary RDS limits, Custom conditions and EC2 operating responsibilities.

Prerequisite

Ordinary RDS provides neither direct host login nor sysadmin for its master user. Engine recovery models and AWS restore mechanisms are also separate concepts.

Compare three management boundaries

The same engine, three operating boundaries
Ordinary RDS

Use supported managed capabilities, with host-access and server-role restrictions.

RDS Custom

Combine managed operation with host customization, within automation and support boundaries.

SQL Server on EC2

Manage the OS and database environment, owning maintenance, protection and recovery.

These are alternatives, not a connection sequence or quality ranking. Check version, edition, Region and usage conditions for each.

Compare control together with operating work
AspectOrdinary RDSRDS CustomEC2
Host OSNo direct loginCustomization within a support perimeterCustomer-managed
MaintenanceSupported mechanisms and maintenance settingsCoordinate with automation and its limitationsCustomer plans OS and engine updates
DB privilegesMaster lacks roles such as sysadminCheck Custom-specific privileges and limitsCustomer designs and protects privileges
Availability/recoverySelect supported deployment and restore mechanismsCheck Custom-specific supportCustomer configures, tests and operates

Fix the same application requirements first

Fictional requirements, not a provisioned environment
RequirementStipulated condition
Application and databaseThe same document app, SQL, data size and performance target
Required featuresList required SQL Server types, features and connection methods
Availability and recoveryThe same failure assumptions, RTO, RPO and retention
Operations teamRecord maintenance capacity and available OS/DB expertise
Cost assumptionsThe same Region, version, edition, duration, capacity and usage terms

A feature matrix is a starting point. If ordinary RDS cannot meet a mandatory requirement, preserve the requirement while evaluating alternatives. Do not treat an older comparison as current feature authority: check engine/service documentation and apply the same requirements to Custom and EC2.

Custom is a distinct operating model

RDS Custom permits host-software customization, but changes must respect automation and its support perimeter. It is not ordinary RDS with unlimited extra host control and no additional responsibility. Work that pauses automation also requires consideration of monitoring and instance-recovery implications.

On EC2, the customer manages the OS and database environment. Configuration control does not complete maintenance or recovery for you. Include ownership of OS/engine updates, security, privileges, backups, availability and restore testing in the comparison.

Equal vCPU counts do not establish equal total costs

Ordinary RDS now has License Included and BYOM arrangements, so BYOM alone does not make EC2 the only option. Custom has its own licensing conditions. Check version, edition, Region, terms and purpose; Developer is neither a production entitlement nor free AWS infrastructure.

Align the assumptions used in a cost comparison
CategoryInclude in the comparison
Compute, storage and transferRuntime, deployment, capacity, I/O, backup retention and transfer assumptions
LicensingLI/BYOM, edition, supported version and contractual eligibility
Operating workUpdates, monitoring, incident response, restore tests and staff time
Meeting the objectivesResources and work needed for availability, recovery and performance

Change a requirement and preserve the unresolved checks

Three fictional cases: preserve the conditions behind the decision
ConditionCandidate and next check
Mostly SELECT, with no custom host operationConsider ordinary RDS, checking support, terms and recovery targets
A custom OS agent is mandatoryCompare Custom support/persistence conditions with EC2 operating work
A mandatory feature is unsupported in ordinary RDSPreserve it and evaluate Custom/EC2 alongside version, edition and maintenance capability
  1. Separate mandatory from optional requirements.
  2. Check restrictions and operating ownership against the sources.
  3. Compare under matched availability, recovery and cost assumptions.
  4. Record the decision and unresolved checks; plan live validation as a separate stage.

Choose an option to see the result and explanation.

If custom host OS operations are required, what deserves evaluation?
Read the answer and reason

Answer: Requirements and responsibilities of RDS Custom or EC2 · Ordinary RDS host-access limits matter.

How should cost and licensing be compared?
Read the answer and reason

Answer: Fix deployment, edition, version, Region and usage terms · No universal cheap/free conclusion is justified.

Can a feature matrix make RDS Custom equivalent to ordinary RDS?
Read the answer and reason

Answer: No; also check operations, maintenance and OS conditions · A single feature matrix cannot capture operational boundaries.

Check, then explain in your own words

  1. Explain how operating work differs across the three options.
  2. Compare without changing the application requirements.
  3. Record evidence and unknowns beyond feature, licensing or price labels.
Check your understanding: If ordinary RDS cannot provide a required host operation, should you immediately choose EC2?

Compare Custom and EC2 support conditions and operating work under the same requirements.

Excluding one option and establishing that an alternative meets the requirements are separate decisions.

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.