Cloud delivery
Cloud Delivery Architecture
The AWS delivery pattern behind shanebaker.cloud using Route 53, CloudFront, S3 static website hosting, ACM, versioning, and a controlled deployment workflow.
The portfolio uses a deliberately simple AWS architecture: static content in S3, secure global delivery through CloudFront, DNS in Route 53, and TLS managed by ACM.
A professional portfolio needs reliable HTTPS delivery, predictable cost, simple updates, recoverability, and enough structure to support future interactive services without unnecessary runtime complexity.
Capability layers and operating flow
This diagram is a conceptual portfolio artifact. Specific products, integrations, controls, and ownership would be confirmed during discovery.
Visitor
shanebaker.cloud
www.shanebaker.cloud
HTTPS requests
DNS and TLS
Route 53 alias records
ACM certificate
Root and www domains
Delivery
CloudFront distribution
Edge caching
Compression
Custom errors
Origin
S3 static website
HTML, CSS, JS
Versioned objects
Operations
Staged upload
Origin testing
Cache invalidation
Rollback through versions
Rules that shape the architecture
Static first
Use the lowest-complexity architecture that fully supports the portfolio.
Test origin before publishing
Validate S3 content before clearing CloudFront caches.
Recovery is designed in
S3 versioning preserves overwritten objects and supports rollback.
ADR 007 — Deliver the portfolio through CloudFront and S3
Decision
Use S3 static website hosting as the origin, CloudFront for HTTPS and caching, Route 53 for DNS, and ACM for certificate management.
Reason
This pattern provides global delivery and professional security with low operating cost and minimal maintenance.
Expected impact
- Low-cost production hosting
- Secure custom-domain delivery
- Simple deployment and rollback process
This is a conceptual architecture decision for portfolio demonstration. Outcomes are design objectives, not claims of measured results for a specific organization.