Cloud architecture for the live portfolio platform.

This page documents the AWS architecture used to publish and deliver the CX Architecture Portfolio as a production grade static website. The platform is designed to be low cost, secure, globally distributed, and easy to maintain.

Architecture Summary

Hosting Model

The portfolio is deployed as a static website on AWS using Amazon S3 for origin storage, Amazon CloudFront for secure global delivery, AWS Certificate Manager for TLS, and Route 53 for DNS. This architecture keeps operating cost low while still following a production ready delivery pattern.

User Entry Point

Public Web Access

Users access the portfolio through the shanebaker.cloud domain over HTTPS.

DNS Layer

Amazon Route 53

Route 53 hosts the public DNS zone for shanebaker.cloud and routes traffic to CloudFront using alias records for the root and www domains.

Delivery Layer

Amazon CloudFront

CloudFront provides HTTPS, edge caching, compression, low latency delivery, and custom domain support for the portfolio site.

Security Layer

AWS Certificate Manager

ACM provides the TLS certificate for shanebaker.cloud and www.shanebaker.cloud, enabling encrypted delivery through CloudFront.

Origin Layer

Amazon S3

S3 stores the static site files including HTML, CSS, architecture pages, and image assets. CloudFront serves the site from this origin.

Architecture Explanation

The portfolio is intentionally deployed as a static site because the primary content is documentation, diagrams, and recruiter facing architecture pages. A static hosting model removes unnecessary runtime complexity while still supporting professional delivery quality.

Amazon S3 acts as the content origin for the site. The root of the bucket stores the main entry files such as index.html and styles.css, while subfolders store architecture pages and visual assets. This keeps the content structure easy to manage and easy to deploy.

Amazon CloudFront sits in front of S3 and handles global delivery. It provides HTTPS, content caching, compression, and low latency performance for users accessing the site. CloudFront also enables the use of the custom domain and protects the site behind a clean delivery layer rather than exposing S3 directly.

AWS Certificate Manager provides the TLS certificate used by CloudFront. This enables secure delivery for both shanebaker.cloud and www.shanebaker.cloud without manual certificate management.

Amazon Route 53 provides authoritative DNS for the domain and routes traffic to the CloudFront distribution through alias records. This creates a clean production pattern that is simple, cost effective, and easy to extend later.

Security and Delivery Design

Delivery Design
Production Ready Static Hosting Pattern
Security Model

HTTPS is enforced through CloudFront using an ACM managed certificate. Public DNS is controlled through Route 53, and site delivery is routed through CloudFront rather than exposing raw origin URLs as the primary access path.

Performance Model

CloudFront edge delivery and object compression improve site performance while keeping infrastructure simple. Static content is cached globally, reducing latency and origin load.

Operating Model

Site updates are managed by editing local files, uploading the site contents to S3, and invalidating CloudFront when needed. This supports clean low overhead maintenance.

Business Impact

Business Impact
Why This Hosting Architecture Matters
Value
  • Low cost production grade hosting architecture
  • Global delivery through CloudFront edge locations
  • Secure HTTPS delivery with ACM managed TLS
  • Simple deployment workflow with minimal operational overhead
  • Clean extension path for future APIs, chatbot flows, and recruiter lead capture

Architecture Decision Record

Architecture Decision Record
ADR 006 — Static Portfolio Delivered Through CloudFront and S3
Decision

The portfolio should be delivered as a static site using Amazon S3 as the origin, Amazon CloudFront as the secure delivery layer, AWS Certificate Manager for TLS, and Route 53 for DNS.

Reason

The site is documentation heavy, low change, cost sensitive, and recruiter facing. A static hosting model provides the right balance of cost efficiency, reliability, security, and simplicity.

Impact
  • Very low operating cost
  • Minimal runtime complexity
  • Strong delivery performance and HTTPS support
  • Easy path to add API driven features later

Related Pages

CX Architecture Blueprint

View the full architecture system map and navigate the complete CX architecture portfolio.

Open blueprint →

Customer Experience Operating System

See the master architecture that organizes channels, automation, service operations, customer records, and intelligence as one coordinated platform.

Open master architecture →