AWS Well-Architected Framework is ArchOps

As I study for my AWS Certified Cloud Practitioner (CCP) certification and knowing that there are a couple of Well-Architected Framework questions on the exam, I decided to take a closer look at the most recent version (Publication date: April 10, 2023).

It's 573 pages!

Really, that seems like a lot?

AWS describes the Well-Architected Framework as "...a collection of best practices that allow customers to evaluate and improve the design, implementation, and operations of their workloads in the cloud."

Ok, but 573 pages!

I knew I had to be missing something, so...

I spent most of the day exploring the Well-Architected Framework by creating a mind map.

Well-Architected is comprised of six pillars

1. Operational Excellence
2. Security
3. Reliability
4. Performance Efficiency
5. Cost Optimization
6. Sustainability

• Each pillar has its own design principles and best practice areas.
• Each best practice area has 1-6 questions that we need to ponder.
• Each question can have "n" best practices. It is at this level that we begin to see actionable content that can be applied to specific solutions.

As my mind map expanded, I came to a personal epiphany!

Unless a representative of AWS architecture contacts me and convinces me otherwise...

Well-Architected is about adopting/developing the philosophy and practice of ArchOps!

Well-Architected is less about specific solution architecture and more about developing the practice and operation of ArchOps.

• There is no question that solutions will absolutely benefit as an architecture PRODUCT of the PROCESS, but the Well-Architected Framework at its essence is about building/developing an ArchOps practice.
• Also, best practices provide should inform our solutions.

IT Services Operations Meta Model: *Ops

Given popular IT group intersections like DevOps should we start thinking more about Operations at the center with various intersections with other major groups (e.g., Development, Testing, Data, and Architecture (...I am including security here instead of breaking out SecOps)). Every company has at least one of the *Ops, but perhaps it is time to look the IT Services Operating Model as holistic set of overlapping groups and interest perspectives?