CLOUD ENGINEERING • AWS • LINUX • FINOPS
Building cloud solutions around the business capabilities that matter.
I approach cloud engineering from the problem outward. Understand the requirement. Design deliberately. Build securely. Verify the result.
AWS CREDENTIALS
Certified knowledge. Applied through real engineering work.
AWS Certified Solutions Architect – Associate
Architecture, resilience, security, performance, and cost-aware AWS design.
Verify credential →FEATURED ENGINEERING
Solutions built from business requirements.
Selected engagements demonstrating architecture decisions, implementation, verification, and lessons learned.
AWS ARCHITECTURE
Production Web Tier
Translated availability and scaling requirements into a resilient web tier using load balancing, Auto Scaling, health checks, and monitoring.
View Engineering Evidence →CLOUD SECURITY
The S3 Bucket Was Public
A security investigation into what public cloud storage actually means, how exposure happens, and why configuration must be verified with evidence.
Read the Story →LINUX / NETWORK SECURITY
Every Open Port Is a Decision
A reflection on firewall rules, exposed services, and learning to treat every open port as an intentional security decision rather than a configuration step.
Read the Story →LIVE AWS PLATFORM
Cloud Engineering Portfolio
Designed this portfolio as a production-style cloud platform with secure delivery, serverless application logic, persistent state, observability, and cost controls.
View Engineering Evidence →HOW I ARCHITECT
Start with the capability. Let the technology earn its place.
I use a repeatable reasoning model to move from business need to verified implementation.
01
Business Capability
What outcome must the organization or user achieve?
02
Technical Requirement
What must the system do to support that outcome?
03
Architecture Decision
What design best satisfies the requirement and constraints?
04
Implementation
Build the smallest solution that satisfies the design.
05
Verification
Prove the system behaves as intended through evidence.
AWS services are implementation choices. The problem comes first.
LIVE CLOUD ARCHITECTURE
You are currently using one of the systems documented in this portfolio.
docdott.com is delivered through a production-style AWS architecture designed around secure delivery, managed services, persistent state, observability, and cost awareness.
IDENTITY
Route 53
Resolves docdott.com to the public delivery layer.
DELIVERY
CloudFront
Provides HTTPS delivery, edge caching, and controlled origin access.
STATIC ORIGIN
Private Amazon S3
Stores the portfolio assets while blocking direct public access.
APPLICATION PATH
Dynamic features use a separate serverless path.
01
Browser
JavaScript sends application requests.
02
API Gateway
Receives and routes API requests.
03
Lambda
Validates requests and executes application logic.
04
DynamoDB
Persists visitor and guestbook state.
AWS WAF
Request protection
IAM
Least-privilege authorization
CloudWatch
Operational visibility
AWS Budgets
Financial guardrails
LIVE VISITOR COUNT
Loading...
LET'S BUILD SOMETHING THAT MATTERS
Architecture should solve the problem before it showcases the technology.
I bring consistency to the work, discipline to the architecture, and a business reason behind every technical decision.
If your team needs someone who can stay with the problem, understand what matters, and architect toward the outcome, let's talk.
ENGINEERING GUESTBOOK
Leave a professional note.
Comments are reviewed before appearing publicly.
Approved Comments