Simple Site. All the Services

Engineering depth across infrastructure, delivery, security, automation, and observability.

Not minimal by design: built to demonstrate implementation depth across AWS service boundaries

18Deliberate Architecture Steps
11AWS Services33AWS Service Components
Monthly Cost

Website Delivery 19 components

  1. Route 53
    1. Hosted Zone
    2. Geolocation Alias Records for `www` (ZA, GB, default)
    3. Geolocation Alias Records for apex (ZA, GB, default)
  2. Certificate Manager
    1. API Gateway Certificate (af-south-1, eu-west-1)
    2. CloudFront Distribution Certificate (us-east-1)
  3. API Gateway
    1. API's (af-south-1, eu-west-2)
    2. Custom Domain Names (af-south-1, eu-west-2)
    3. API Integration Lambda Function (af-south-1, eu-west-2)
  4. Lambda
    1. Geolocation Redirect Functions (af-south-1, eu-west-2)
    2. Geolocation Function Invoke Permissions
  5. IAM
    1. Geolocation Function Execution Role
    2. Geolocation Role Policy Attachment
  6. CloudWatch
    1. Geolocation Function Log Groups (af-south-1, eu-west-2)
  7. CloudFront
    1. Website Distribution
    2. Edge Redirect Function
    3. Origin Access Control
    4. Response Headers Policy
  8. S3
    1. Website Bucket
    2. Bucket Access Controls, Encryption, Versioning, and Policy

Cost Telemetry 14 components

  1. EventBridge
    1. Schedule Rule
    2. Schedule Target
  2. DynamoDB
    1. Application Table
    2. Stream
  3. SQS
    1. Cost Updates Queue
  4. Lambda
    1. Cost Function
    2. SQS Event Source Mapping
    3. Invoke Permission from EventBridge
  5. IAM
    1. Cost Function Role
    2. Cost Function Inline Policy
    3. Cost Function Role Policy Attachment
    4. Pipe Role
    5. Pipe Inline Policy
  6. EventBridge Pipes
    1. DynamoDB Stream to SQS Pipe

Intentional complexity here is a capability test, not a recommendation for every workload

Maximum AWS, Minimum Site architecture diagram