Inspired by the Pacific coast

Room for a little more life.

Thoughtful interiors for homes and neighbourhood businesses. Natural materials, a clear purpose, and spaces that welcome you in.

Explore the studio design

An original fictional business, created for a real cloud engineering project.

CEDAR / LIGHT / STILLNESS

01 / Listen

Your everyday comes first.

We begin with how you live and work, then design a space around it.

02 / Simplify

Good choices, made clear.

Honest materials, considered layouts, and a practical plan for moving forward.

03 / Belong

Built to feel like you.

Places with warmth and purpose, rooted in the communities they serve.

The original WordPress design

A considered space,
a practical purpose.

Cedar & Tide is a fictional design studio. The brand, theme, copy and CSS room illustration belong to the CloudPress demonstration. This preview preserves the design after the short-lived AWS exercise.

No enquiries, login, shopping or personal-data forms operate on this preview.

Residential interiors

Room planning, material selection, and a practical design brief that fits your routine.

Small business spaces

Welcoming shops, cafés, and studios designed around how your team and customers move.

Design consultations

A focused conversation, a clear direction, and a useful next-step plan.

Behind the experience

A website designed to be replaceable.
Content designed to stay.

The AWS implementation separates public delivery, application releases and persistent data. This diagram describes the lab architecture; it is not a live infrastructure monitor.

Public delivery

CloudFront → Application Load Balancer

HTTPS viewer access · controlled origin ingress

Private application

EC2 Auto Scaling · Nginx · PHP · WordPress

Versioned releases · one-host-at-a-time delivery

Persistent state

RDS MySQL + shared EFS uploads

Private database · managed secrets · encrypted storage

The engineering case study

The decisions. The difficulties.
The evidence behind the claims.

Source code and diagrams explain the intended behavior. The test record separates executed checks from unrun exercises, and the build journal records the account-plan restriction that led to the SSM delivery driver.

01 / Validation

Recorded tests & limits

Local checks, live observations and remaining acceptance tests.

02 / Engineering

What proved difficult

The actual blockers, fixes and reasoning behind the implementation.

03 / Trust boundaries

Security & IAM

Private tiers, separated credentials and explicit production gaps.

04 / Responsible operation

Cost & teardown

A bounded promotional-credit exercise with full workload cleanup.

A preview, not a running CMS. GitHub Pages serves these static files. The genuine WordPress application, Terraform and AWS pipeline remain in the repository. Screenshots and test records carry the deployment evidence; this page does not simulate a successful deployment, current uptime or live metrics.

Browse the evidence folder

Explore the implementation

Good design goes deeper
than the page.

Explore CloudPress on GitHub Read the architecture decisions