What Is the AWS Well-Architected Framework?
The AWS Well-Architected Framework is a structured set of architectural best practices developed by AWS over years of reviewing thousands of customer workloads. It gives cloud architects a consistent way to evaluate designs, identify risks, and make informed trade-offs. Rather than prescribing a single correct architecture, it provides a set of guiding questions across six pillars, helping teams understand the implications of every design decision.
For African enterprises where cloud adoption is accelerating rapidly, the framework is particularly valuable. It prevents the common pattern of teams migrating quickly to AWS and then spending months retroactively fixing security gaps, reliability issues, and inefficient spending. A Well-Architected Review conducted before or shortly after migration identifies these risks before they become costly production incidents.
The Six Pillars Explained
Each pillar maps to a distinct concern, with its own design principles and review questions. Use the table below as a quick reference, then read the deeper notes on each pillar that follow.
| Pillar | Core question it answers | Key AWS services |
|---|---|---|
| Operational Excellence | How do we run, monitor, and improve workloads? | Systems Manager, CloudWatch, CloudFormation |
| Security | How do we protect data, identities, and systems? | IAM, KMS, GuardDuty, Security Hub |
| Reliability | How do we recover from failure and meet SLAs? | Multi-AZ, Auto Scaling, Route 53, Backup |
| Performance Efficiency | Are we using the right resources for the workload? | Compute Optimizer, Trusted Advisor, Graviton |
| Cost Optimisation | Are we spending only on what delivers value? | Cost Explorer, Savings Plans, Budgets |
| Sustainability | How do we reduce environmental impact? | Graviton, Spot Instances, AWS Customer Carbon Footprint Tool |
1. Operational Excellence
This pillar focuses on running and monitoring systems to deliver business value and continually improving processes and procedures. The design principles include:
- Perform operations as code — define your infrastructure and operations in version-controlled templates.
- Make frequent, small, reversible changes — never ship a big-bang release.
- Refine operations procedures frequently — runbooks should be living documents.
- Anticipate failure — practise incident response before you need it.
Practically, this means your team should be writing runbooks, running game days, and using AWS Systems Manager for automated operations rather than relying on manual SSH access.
2. Security
The Security pillar covers the ability to protect data, systems, and assets while delivering business value. AWS recommends a strong identity foundation, enabling traceability through comprehensive logging, applying security at all layers, automating security best practices, and protecting data in transit and at rest. For African enterprises subject to local data-protection legislation, the Security pillar provides a direct mapping between AWS controls and regulatory requirements.
3. Reliability
Reliability is your workload's ability to perform its intended function correctly and consistently, including recovery from infrastructure or service disruptions.
- Multi-AZ deployments and automatic recovery as the default
- Horizontal scaling instead of vertical scaling where possible
- Graceful degradation for intermittent network conditions — particularly relevant in some African markets
4. Performance Efficiency
Use computing resources efficiently to meet requirements, and maintain efficiency as demand changes and technology evolves.
- Right-size instance types continuously — this alone usually finds material savings
- Reach for serverless where the workload shape allows it
- Experiment with newer services (Graviton, faster EBS, newer instance families) on a cadence
5. Cost Optimisation
Avoid unnecessary spend and understand where every dollar goes. Most organisations reduce their AWS bill by 20–35% in their first review cycle.
- Cost Explorer with team-level tagging from day one
- Savings Plans / Reserved Instances on stable, predictable workloads
- Budget alerts on every account, reviewed monthly
- Quarterly hunt for unused resources — snapshots, IPs, unattached volumes
6. Sustainability
Added in 2021. Minimise the environmental impact of cloud workloads, with measurable carbon accounting.
- Maximise utilisation — idle compute is the largest waste source
- Choose Graviton instances where compatible (better perf-per-watt)
- Use the AWS Customer Carbon Footprint Tool for ESG reporting
Using the Well-Architected Tool
The AWS Well-Architected Tool is a free service in the AWS Console that guides you through a structured questionnaire for each pillar. After completing the questions, the tool produces a report classifying issues as High Risk Issues (HRIs) or Medium Risk Issues (MRIs), along with recommended improvement actions linked directly to AWS documentation.
The tool supports custom lenses, allowing organisations to overlay industry-specific or organisation-specific questions on top of the standard pillar questions. For example, a financial services institution might add a custom lens covering Central Bank of Kenya digital infrastructure requirements, creating a single consolidated risk view that covers both AWS best practices and local regulatory obligations.
AWS recommends running reviews on a milestones basis: before launch, at significant architectural changes, and at least annually. Each milestone snapshot is saved in the tool, creating an audit trail of your architectural evolution over time.
Applying the Framework in Africa
The Well-Architected Framework is global by design, but its application in Africa has some distinctive characteristics worth understanding.
On Reliability, the intermittent connectivity experienced in some markets means teams should prioritise asynchronous architectures that queue requests locally and process them when connectivity is restored. Amazon SQS and AWS Step Functions are particularly useful here. Multi-AZ deployments within the Cape Town region (af-south-1) provide the same intra-region redundancy as any other AWS Region, and organisations serving East African customers can combine af-south-1 with eu-west-1 or me-south-1 for geographic resilience.
On Security, regulatory requirements vary significantly by country and sector. The Kenya Data Protection Act, Nigeria's NDPR, and South Africa's POPIA each impose distinct lawful-basis, security, and breach-notification obligations. A Well-Architected Review is an effective vehicle for mapping these regulations onto concrete AWS service configurations.
On Cost Optimisation, foreign-currency billing can be a challenge in markets with volatile exchange rates. Purchasing Reserved Instances or Savings Plans in advance locks in a predictable USD commitment, which some treasury teams find easier to manage than variable monthly invoices. AWS also offers billing support in local currencies for select markets.
Partner-Led Reviews with Kitstek
As an AWS Advanced Partner, Kitsilano Technologies conducts Well-Architected Reviews for customers across East and Southern Africa. Partner-Led Reviews follow the same structure as self-assessments but include hands-on support from our certified architects throughout the process. Qualifying customers receive the review at no charge as part of the AWS Partner-Led Support programme.
Our review engagements typically run across two days. On day one, we walk through the six-pillar questionnaire with your engineering and operations teams. On day two, we present a remediation roadmap prioritised by risk level and business impact, with estimated effort and AWS service recommendations for each item. Post-review, we can implement remediations directly or support your internal team as they work through the backlog.
Frequently Asked Questions
A standard AWS Well-Architected Review typically takes one to three days depending on the complexity of your workload. Kitsilano Technologies conducts reviews as structured workshops, walking through each pillar with your architecture and engineering teams. The output is a prioritised risk register with recommended remediations so your team can act immediately.
Yes. The AWS Well-Architected Tool in the AWS Console is available at no charge. You pay only for any AWS resources used during the review or remediation process. As an AWS Advanced Partner, Kitsilano Technologies can also conduct Partner-Led reviews at no cost to qualifying customers.
A Well-Architected Review is a structured self-assessment guided by AWS best practices across six pillars. An audit is typically a formal third-party examination against a compliance standard such as ISO 27001 or PCI-DSS. Reviews are proactive and improvement-focused, while audits are retrospective and compliance-focused. The two approaches are complementary and work well together.
Most African enterprises benefit from starting with the Reliability and Cost Optimisation pillars. Reliability addresses the connectivity and redundancy challenges common in the region, while Cost Optimisation ensures AWS spend is aligned with actual business value before the environment grows further.



