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.
Compare three deployments under matched requirements and explain ordinary RDS limits, Custom conditions and EC2 operating responsibilities.
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
Use supported managed capabilities, with host-access and server-role restrictions.
Combine managed operation with host customization, within automation and support boundaries.
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.
| Aspect | Ordinary RDS | RDS Custom | EC2 |
|---|---|---|---|
| Host OS | No direct login | Customization within a support perimeter | Customer-managed |
| Maintenance | Supported mechanisms and maintenance settings | Coordinate with automation and its limitations | Customer plans OS and engine updates |
| DB privileges | Master lacks roles such as sysadmin | Check Custom-specific privileges and limits | Customer designs and protects privileges |
| Availability/recovery | Select supported deployment and restore mechanisms | Check Custom-specific support | Customer configures, tests and operates |
Fix the same application requirements first
| Requirement | Stipulated condition |
|---|---|
| Application and database | The same document app, SQL, data size and performance target |
| Required features | List required SQL Server types, features and connection methods |
| Availability and recovery | The same failure assumptions, RTO, RPO and retention |
| Operations team | Record maintenance capacity and available OS/DB expertise |
| Cost assumptions | The 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.
| Category | Include in the comparison |
|---|---|
| Compute, storage and transfer | Runtime, deployment, capacity, I/O, backup retention and transfer assumptions |
| Licensing | LI/BYOM, edition, supported version and contractual eligibility |
| Operating work | Updates, monitoring, incident response, restore tests and staff time |
| Meeting the objectives | Resources and work needed for availability, recovery and performance |
Change a requirement and preserve the unresolved checks
| Condition | Candidate and next check |
|---|---|
| Mostly SELECT, with no custom host operation | Consider ordinary RDS, checking support, terms and recovery targets |
| A custom OS agent is mandatory | Compare Custom support/persistence conditions with EC2 operating work |
| A mandatory feature is unsupported in ordinary RDS | Preserve it and evaluate Custom/EC2 alongside version, edition and maintenance capability |
- Separate mandatory from optional requirements.
- Check restrictions and operating ownership against the sources.
- Compare under matched availability, recovery and cost assumptions.
- Record the decision and unresolved checks; plan live validation as a separate stage.
Choose an option to see the result and explanation.
Check, then explain in your own words
- Explain how operating work differs across the three options.
- Compare without changing the application requirements.
- 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.
Scope and conditionsOrdinary RDS SQL Server, version-specific support and restricted direct host access.
Used in this lessonCompare three management boundaries Change a requirement and preserve the unresolved checks
- SQL Server security on RDSChecked:
Scope and conditionsOrdinary RDS master-user roles and unavailable sysadmin, separate from IAM.
Used in this lessonCompare three management boundaries Change a requirement and preserve the unresolved checks
Scope and conditionsHost customization within automation boundaries, including monitoring/recovery implications of a pause.
Used in this lessonCompare three management boundaries Custom is a distinct operating model Change a requirement and preserve the unresolved checks
Scope and conditionsVersion/Region and support conditions; persistence restrictions for OS changes without a CEV.
Used in this lessonCompare three management boundaries Custom is a distinct operating model Change a requirement and preserve the unresolved checks
- Amazon EC2 for SQL ServerChecked:
Scope and conditionsSelf-managed SQL Server: customer ownership of OS, database, protection, replication and recovery.
Used in this lessonCompare three management boundaries Custom is a distinct operating model Change a requirement and preserve the unresolved checks
Scope and conditionsVersion-specific restrictions including TLS1.3/MS-TDS8.0 for SQL Server2022.
Used in this lessonFix the same application requirements first
Scope and conditionsA comparison framework; current feature support must be checked in service documentation, not inferred from every matrix cell.
Used in this lessonFix the same application requirements first
- SQL Server licensing on RDSChecked:
Scope and conditionsOrdinary RDS LI/BYOM and edition conditions; no individual eligibility ruling.
Used in this lessonEqual vCPU counts do not establish equal total costs Change a requirement and preserve the unresolved checks
- BYOM for RDS SQL ServerChecked:
Scope and conditionsOrdinary RDS BYOM is conditional; installation media does not establish OS access.
Used in this lessonEqual vCPU counts do not establish equal total costs Change a requirement and preserve the unresolved checks
- Developer Edition on RDSChecked:
Scope and conditionsNon-production development/testing; separate SQL Server licensing from AWS infrastructure charges.
Used in this lessonEqual vCPU counts do not establish equal total costs
- BYOM with RDS Custom SQL ServerChecked:
Scope and conditionsReview Custom LI/BYOM conditions separately from ordinary RDS.
Used in this lessonEqual vCPU counts do not establish equal total costs