PERSONAL PROJECT · AI-ASSISTED · SYNTHETIC DATA · READ-ONLY

Infrastructure Design Validator

I built this sample report to flag selected network, ownership, dependency, and recovery issues. It does not inspect live cloud systems or certify an architecture.

4 components · 3 subnets · 4 review findings

The diagram shows the connections supplied in the sample design. Public connections are listed below. Backup capacity is supplied information, not verified.

Design review checklist

Check	System (technical ID)	Action
Single-instance riskTechnical code: `REDUNDANCY`	app-service	Review a single-instance component supporting a high-criticality workload.
Accountable owner missingTechnical code: `OWNER`	database	Confirm an accountable technical owner.
Recovery evidence needs reviewTechnical code: `RECOVERY`	database	Validate recovery evidence against workload recovery objectives.
Public access needs reviewTechnical code: `PUBLIC_ADMIN_DATA`	database	Review public access on port 1433; document intended restricted access.

Proposed setup order

Stage 1: database, identity-service
Stage 2: app-service
Stage 3: web-gateway

Systems without a setup order: None. These groups show which systems depend on others, not scheduled dates or an approved deployment.

Connections in the sample design

internet → web-gateway · port 443
web-gateway → app-service · port 443
app-service → identity-service · port 443
app-service → database · port 1433
internet → database · port 1433

No cloud resources were created or changed. The tool checks selected network ranges, connections, owners, recovery records, backup capacity, and public ports in the sample. These checks do not replace a full architecture or security review.