Presley John

Assess. Design. Prove.

From the Origins to...
A journey of continuous evolution.

A portfolio of infrastructure, cloud, web, and operational systems.
Built through practice, clarity, and real-world problem solving.

Infrastructure / Connectivity / Assessment

Infrastructure and connectivity that support real work.

A clear view of how users, networks, applications, security, and operations connect before recommending changes.

Infrastructure and connectivity assessment map
Assessment Focus

Users & Workflows

The first step is understanding how people actually work: employees, guests, vendors, remote users, and shared devices. This reveals access gaps, workflow friction, and places where permissions or device use may create operational risk.

Ready to map your environment?
  • Clarify what you have
  • Find weak points
  • Plan practical improvements
Start Review
Cloud / Automation / Operations

Cloud systems with operational memory.

AWS foundations, Terraform baselines, monitoring, alerting, documentation paths, and operational signals that prove the environment is not just designed β€” it is running.

Architecture

Public entry, private app, private data.

The topology shows a controlled AWS pattern: public ingress, private application services, private data, and supporting access paths kept intentionally segmented.

AWS ingress, application, and data architecture diagram
Public ingress, application layer, private services, data layer, and controlled access paths shown as one operating pattern.
Reproducibility

Builds that can be recreated and checked.

Terraform initialization and validation prove the baseline is not hand-waved. The environment can be reviewed, repeated, and improved safely.

Terraform init and validate proof from AWS CloudShell
Terraform init and validate confirm the configuration path is repeatable.
Primary and baseline validation environments
Separate primary and validation footprints support safer testing and repeatable review.
Operations

Run state, health, and alerting are part of the story.

Health checks, target state, CloudTrail filters, and alert summaries show that the environment is observable, not just diagrammed.

Healthy target state signal from the load balancer
Healthy target state confirms the service path is active.
Operational alert audit summary
Operational summary keeps alerting and review points visible.
Documentation

Structure makes the environment easier to operate.

Organized S3 documentation paths, subnet naming, architecture folders, and runbooks reduce ambiguity and make future review easier.

S3 documentation folder structure
Documentation paths are grouped by architecture, security, SRE, Terraform, and workflows.
AWS subnet naming structure
Consistent subnet naming improves visibility while sensitive values stay masked.

WEB / EXPERIENCES

Sites built for experience.

Digital presence, appointment paths, event pages, and landing pages designed with structure, motion, and purpose.

Built to Guide Action

Clear pages that help people understand the offer, trust the path, and take the next step.

Digital Presence

Business websites

Simple, polished pages for services, professionals, events, and local brands.

Event experience

Interactive pages for shared moments.

Appointments

Booking paths, request forms, and guided next steps.

Client intake

Structured questions that help start projects clearly.

Landing pages

Focused pages for campaigns, offers, launches, and announcements.

What I’m Building

Hahaii

Hahaii is the larger platform I am building around trust, accountability, and resilient systems. The current focus is attendance and operational logic designed to be reliable, auditable, intuitive to operate, and smooth in everyday use.

Operations taught me systems. Infrastructure taught me structure. Cloud taught me scalability. Security taught me boundaries. Web taught me experience. Automation taught me leverage. MSP life taught me adaptability.
The journey continues.