Implemented portfolio feature

Cloud Resume Telemetry Counter

A small serverless counter adds live telemetry to the static portfolio without collecting visitor identity or exposing private data.

Status Implemented site feature
AWS focus
API GatewayLambdaDynamoDBCloudWatchFree Tier
CF
Static CloudFront site CloudFront
API
API Gateway HTTP API API Gateway
L
Lambda telemetry handler Lambda
DDB
DynamoDB provisioned table DynamoDB
AWS
Aggregate view count

Problem

A cloud resume site benefits from one small live AWS feature, but the implementation should not store IP addresses, emails, user agents, or other visitor identifiers. It should also stay inside free-tier-friendly service choices.

Design

  • The homepage calls an API Gateway HTTP API endpoint.
  • Lambda increments aggregate counters using DynamoDB atomic updates.
  • DynamoDB uses Standard table class with provisioned 25 RCU and 25 WCU capacity.
  • The frontend uses localStorage to avoid counting the same browser repeatedly throughout the same day.
  • CloudWatch logs are retained for 14 days and do not include visitor identity data.

Cost controls

The DynamoDB table uses provisioned capacity inside the always-free allowance for this portfolio account. Lambda uses 128 MB memory and a 5-second timeout. API Gateway stage throttling limits request rate to a small burst and steady-state rate.

Privacy controls

Only two aggregate counter records are stored: all-time site views and today's views. The system does not store IP address, email address, browser fingerprint, or page-level visitor identifiers.