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

What is Amazon RDS? Managed responsibilities and database engines

Amazon RDS is a service that shares relational-database management work with AWS. Use a document application to distinguish the database engine, connectivity, availability and recovery. Managed infrastructure still leaves decisions about SQL, permissions and data with the customer.

What you will learn

Explain the managed boundary and evaluate engine, availability and recovery as separate requirements.

Prerequisite

A database organizes data; SQL expresses requests to a relational database. Distinguish the application client from its database target.

Separate managed operations from application decisions

Choose a supported database engine and deployment in RDS. An engine is the database software that processes SQL and data. RDS supplies managed operation around it; features and responsibilities depend on the engine and deployment.

Two management boundaries in a document application
Managed by AWS

Provides infrastructure and supported maintenance, backup and availability mechanisms; customers select their configuration.

Customer decisions

Design document tables, SQL, database identities, allowed clients and retention/recovery requirements.

This is a responsibility map, not a network sequence or a claim that every engine has identical features.

A slow document search still requires investigation of SQL, indexes and workload. An overly broad SELECT grant is not corrected by an available instance status. A managed capability and an appropriate configuration are different things.

Choose an engine from the application requirements

Match compatibility and operation, rather than choosing by name
QuestionDocument-app example
SQL and application compatibilityIf existing SQL Server types, features and drivers are required, verify support
Features and versionsCheck RDS restrictions by engine version, edition and Region
Operation and costCompare maintenance, recovery targets, capacity and licensing under matched assumptions

Choosing RDS does not make all database engines interchangeable. An engine change requires checks of SQL, types and application behavior, beyond changing an endpoint. This learning path uses SQL Server as a concrete example, while RDS itself supports multiple engines.

Separate available status from application access

Available is a managed instance status. Application access additionally depends on the source and target, DNS and port, network controls, TLS, database login and object permissions. IAM access to the management interface is separate from a database user’s SELECT rights.

Distinguish availability from recovery

Different objectives require different mechanisms
ObjectiveConditions to check
Continue or resume after a failureDeployment such as Multi-AZ, failover, reconnection and application handling
Return to data before a bad updateRetention, restorable point, restore target and application cutover
Retain a backupSnapshot retention and protection; distinguish it from a SQL Server .bak

A Multi-AZ standby is not a historical backup. A bad update can also be replicated, so recovery targets and backups need separate planning. A Multi-AZ DB-instance standby does not serve reads. Distinguish that deployment from a readable Multi-AZ DB cluster, checking engine support rather than assuming every engine supports both.

An RDS DB snapshot is a managed restore mechanism, not the same operation as creating a native SQL Server .bak file. Check its target, granularity and restrictions; the existence of a backup alone does not establish recovery to an arbitrary point.

Apply three decisions to the document application

  1. Existing SQL Server features are required: first check ordinary RDS version, edition and feature support.
  2. The DB is available, but app access is unverified: establish source, path, identity and SELECT evidence.
  3. Documents were updated incorrectly: inspect the restorable point and target, beyond the presence of a standby.

Choose an option to see the result and explanation.

What responsibility remains with an RDS customer?
Read the answer and reason

Answer: Designing database use, app access and permissions · Managed infrastructure does not remove application responsibilities.

Does available mean a client can successfully log in?
Read the answer and reason

Answer: No · It is management state, not network/TLS/auth success.

Is an RDS DB snapshot the same as a SQL Server .bak?
Read the answer and reason

Answer: No; distinct methods and scopes · Snapshots are instance-level; native .bak supports database-level restore.

Check, then explain in your own words

  1. Explain RDS separately from the database engine.
  2. Name two managed tasks and two customer decisions.
  3. Write requirements that distinguish available status, availability and a recovery point.
Check your understanding: Does an available Multi-AZ database establish recovery from a bad document update?

No. The recovery point, retention and restore target still need to be established.

Replication for availability and recovery to a historical state solve different problems.

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.