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

Connecting to RDS for SQL Server: VPC, TLS and SSMS

A connection to RDS for SQL Server involves a network path, TLS, database authentication and object permissions. Follow an SSMS client reading a document list. Learn what an available instance or a reachable port establishes—and what remains unverified—without connecting to a live database.

What you will learn

Fix the source, target, database, principal and time, then separate TCP reachability from certificate validation, login and a SELECT result.

Prerequisite

SSMS is a SQL Server client, a VPC is a virtual network, security groups control traffic, and SELECT permission authorizes a database read. These distinctions are reviewed here.

Start with the source and private database endpoint

RDS for SQL Server shares database-management work between AWS and the customer. Available is an AWS DB-instance status, not evidence that a particular user read a table. Private here means the instance is not directly exposed to the internet.

An endpoint is a DNS hostname identifying the connection target; its port identifies the service receiving traffic. Match both to the intended RDS instance. SSMS is a Windows database client, not a host-OS login tool.

From the client to the database: a private network example
client-A / SSMS

A Windows client with a private path, separate from the application app-A.

VPC path and traffic controls

Review routes, security groups and network access control lists (NACLs) in both directions.

RDS endpoint

db-sql.example.invalid / 1433: a fictional target for rds-demo-1.

Arrows represent requests and responses. example.invalid is fictional: no DNS resolution or connectivity has been measured.

Both source and database are private in this example. An allowed private path does not require a publicly accessible database. Sharing a VPC alone does not establish access: inspect the source, destination port, routes and traffic controls.

Identify one attempt before interpreting evidence

Fictional read conditions used on this page
ItemStipulated condition
Instance and versionrds-demo-1 / ordinary RDS / illustrative SQL Server 2022 Standard
Source and targetclient-A → db-sql.example.invalid:1433, fictional
Database and tableCorpDocs / app.Documents
Database principal and operationreader_demo / SELECT only
Data stateFive independently stipulated T0 rows, with no writes, triggers or additional row filtering

A principal is the login or database user performing the operation. The row values match the earlier SQL Server example, but no synchronization from sql-demo-1 is assumed. Matching table names or SQL do not establish matching results in another database, identity or time. Permission to inspect RDS through IAM is also separate from a SQL Server login.

Separate TLS encryption from server identity validation

TLS protects traffic in transit. Certificate validation checks the trust chain, expected server name and validity period. TCP reachability, encrypted traffic and a validated server identity are distinct observations.

Do not select a setting by its name alone
SettingMeaning and conditions
EncryptionSSMS 20+ offers Mandatory/Optional/Strict; match engine and driver support
Trust server certificateEnabling it bypasses certificate validation; distinguish encryption from identity
Certificate hostname / CAReview the expected name and trust store; network exposure does not fix name or expiry errors

Do not recommend Strict universally because its name sounds stronger. AWS lists TLS1.3 and MS-TDS8.0 restrictions for SQL Server 2022, the engine example here. Check CA, name, validity and client/server compatibility; neither bypassing validation nor exposing the database is a standard repair.

Read three attempts without inventing a successful connection

Every cell is stipulated; these are not live observations
AttemptDNS / path / TCPTLS and server identityDB login / SELECTQuery
A: path onlyStipulated passNot establishedNeither establishedNot run
B: prerequisites fixedStipulated passStipulated passreader_demo login and SELECT stipulatedFour rows inferred from fixture
C: certificate failureStipulated passStipulated failureNot run after TLS failureNot run

Attempt A stipulates only the lower-layer path; do not add a successful login or query. Attempt C stipulates a TLS failure, not a later permission denial. Not established means evidence is missing; not run means no attempt occurred. Neither is the SQL truth value UNKNOWN from a NULL comparison.

Attempt B: T0 documents and the selected predicate
Document IDTitleStatusOwner ID
101Handbookopen1
102Diagramopen1
103Budgetdraft2
104Archiveopen3
105UnassignedopenNULL
Illustrative SELECT text, with no query runner
SELECT document_id
FROM app.Documents
WHERE status = N'open'
ORDER BY document_id;

Under attempt B, the expected document IDs are 101 → 102 → 104 → 105. Document 103 is draft; document 105 remains included because the predicate tests status, not its NULL owner. ORDER BY specifies the unique ID order. This is a fixture calculation, not a live query result.

Choose the next check from the last established fact

  1. Identify the source, intended instance, endpoint, port and attempt time.
  2. Separate DNS, private routing, security groups and applicable NACLs.
  3. After TCP, inspect TLS, CA trust, name, validity and version compatibility.
  4. Establish the database principal, current database, table and SELECT rights.
  5. Match SQL to the data state and distinguish predicted rows from observations.

This is a diagnostic sequence, not an exact SQL Server packet trace. Work from the last established fact: a certificate error does not justify opening a security group to everyone, and a SELECT denial does not establish a need for sysadmin.

Check what each observation establishes

Choose an option to see the result and explanation.

Can client-A reach a private RDS instance using an allowed private path?
Read the answer and reason

Answer: Potentially, if all path controls allow it · Public access is not required for a private path.

TCP succeeded, TLS was not checked. What can we conclude?
Read the answer and reason

Answer: Login and SELECT outcome are unknown · Success at one layer does not establish higher-layer success.

What is the recommended response to a certificate-chain problem in this connection example?
Read the answer and reason

Answer: Review CA trust, expected hostname and client · Check endpoint name, CA trust, validity and client version. Do not generalize a version-specific exception or claim a verified live connection.

Can Strict be recommended for every RDS SQL Server configuration because its name sounds stronger?
Read the answer and reason

Answer: No; check client and engine TLS/TDS support · Separate encryption and identity verification; do not universally recommend unsupported protocols.

Check, then explain in your own words

  1. Describe source, target, database, identity and time together.
  2. Separate available, TCP, TLS, login, authorization and results.
  3. Preserve missing evidence and non-execution; recompute the four fixture rows.
  4. Review certificate and version conditions instead of choosing settings by name.
Check your understanding: Does a successful TCP connection establish that the app can read the documents?

No. TLS, database identity, SELECT rights, SQL and data conditions are separate.

SSMS and the app can also use different sources and identities. Match each conclusion to the particular attempt and evidence.

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.