I’ve been involved with the Well-Architected Framework since my time at AWS when in late 2014 I was asked to participate in the internal discussions defining the concept. I’ve done many assessments, and I’ve used the perspectives to define and influence architectural decisions in workload deployments across the spectrum from startups to enterprises and governments.
The prescribed approach to date has been focused on the recommendations primarily of workloads: well-architected IN the cloud. BUt there’s so much more that has been missed: well-architected OF the cloud.
This has just been addressed in a recent update.
Top Down, bottom up
I have always looked at the way that the client’s AWS cloud estate is implemented from the AWS Account structure – starting with the management account, core Control Tower accounts (Audit, Security), shared services, and then various workload (sets of) accounts. I say “sets of”, as significant workloads may have separation of Development, Testing, UAT, and Production – or perhaps even more. I’ve thought of this as being the “Top-Down” control.
Meanwhile, which each of those workload accounts comes the application(s), and their posture towards the Well-Architected balance. To me that has been the “Bottom-Up” posture.
Somewhere in the middle these two meet, and their union makes happy workloads that meet balance all requirements.
Historically, Well-Architected didn’t address these two areas: it just looked at Workloads and tacked on some organisational level controls along the way. In my approach, I’ve always had a detailed approach to the organisation controls, derived best practice from real-world use protecting and scaling systems for over 16 years in AWS.
That split has now been recognised with todays update:
- AWS Well-Architected Cloud Foundations (WA Cloud Foundations)
- Well-Architected Cloud Workloads (WA Cloud Workloads)
Within enterprise organisations, it is likely different stakeholders will (or should) own responsibility for each of these.
Foundations
The Foundation section adds a set of questions that I have spent the last 10 years asking clients to consider. These are the encompassing cloud services that set the cost governance and risk boundaries across the entire cloud estate – as organised via AWS Organizations and enforced via policies and delegations.
There are times when large organisations may have multiple AWS Organizations: such as different companies in a Group, different or conflicting regulatory requirements around the world, or potentially sheer scaling limits (e.g.: hundreds of thousands of AWS Accounts).
There is also a minimum: every client organisation should have at least one Organization, normally deployed via Control Tower, with strict separation of production workloads from non-production, and with federated identity to the AWS control plane (console, APIs).
While Well-Architected Framework Workloads still has six pillars, Foundations has a different set – seven capabilities of focus:
- FND01 – Multi-Account Environment
- FND02 – Identity and Access Management
- FND03 – Central Observability Managemen
- FND04 – Resource and Inventory Management
- FND05 – Security and Compliance
- FND06 – Cloud Financial Management
- FND07 – Networking and Connectivity
Support in The Well-Architected Tool
At this time, the WAFR tool in the AWS Console does not yet have native support for Foundations, but this is easily fixed using a Custom Lens. Here’s one I created just now, in Github: https://github.com/JamesBromberger/aws-well-architected-foundations-lens
You can add this into the AWS WAFR tool in the console as is, or perhaps fork the Github and improve it!
Running a Well-Architected Review
You’re welcome to run these reviews yourself, but the best benefit is to run them with someone deeply experienced in the concepts. Through Nephology (my consulting brand) I’m available to do this with you.
On your side, you’ll need to determine if you want to focus on the Foundations, a specific Workload, or both. You’ll need your expert available to work with me through a review, which we can do online remotely, or face to face. Please contact me to discuss your requirements as early a possible so we can schedule this in.
Note that repeating a Well-Architected review on an annual basis is a recommendation to gauge the ability of your organisation to progress the remediations, or identify that perhaps they are not being actioned.