Search for Well Architected Advice
-
Operational Excellence
-
- Resources have identified owners
- Processes and procedures have identified owners
- Operations activities have identified owners responsible for their performance
- Team members know what they are responsible for
- Mechanisms exist to identify responsibility and ownership
- Mechanisms exist to request additions, changes, and exceptions
- Responsibilities between teams are predefined or negotiated
-
- Executive Sponsorship
- Team members are empowered to take action when outcomes are at risk
- Escalation is encouraged
- Communications are timely, clear, and actionable
- Experimentation is encouraged
- Team members are encouraged to maintain and grow their skill sets
- Resource teams appropriately
- Diverse opinions are encouraged and sought within and across teams
-
- Use version control
- Test and validate changes
- Use configuration management systems
- Use build and deployment management systems
- Perform patch management
- Implement practices to improve code quality
- Share design standards
- Use multiple environments
- Make frequent, small, reversible changes
- Fully automate integration and deployment
-
- Have a process for continuous improvement
- Perform post-incident analysis
- Implement feedback loops
- Perform knowledge management
- Define drivers for improvement
- Validate insights
- Perform operations metrics reviews
- Document and share lessons learned
- Allocate time to make improvements
- Perform post-incident analysis
-
Security
-
- Separate workloads using accounts
- Secure account root user and properties
- Identify and validate control objectives
- Keep up-to-date with security recommendations
- Keep up-to-date with security threats
- Identify and prioritize risks using a threat model
- Automate testing and validation of security controls in pipelines
- Evaluate and implement new security services and features regularly
-
- Define access requirements
- Grant least privilege access
- Define permission guardrails for your organization
- Manage access based on life cycle
- Establish emergency access process
- Share resources securely within your organization
- Reduce permissions continuously
- Share resources securely with a third party
- Analyze public and cross-account access
-
- Perform regular penetration testing
- Deploy software programmatically
- Regularly assess security properties of the pipelines
- Train for Application Security
- Automate testing throughout the development and release lifecycle
- Manual Code Reviews
- Centralize services for packages and dependencies
- Build a program that embeds security ownership in workload teams
-
-
Reliability
-
- Be aware of service quotas and constraints in Cloud Services
- Manage service quotas across accounts and Regions
- Accommodate fixed service quotas and constraints through architecture
- Monitor and manage quotas
- Automate quota management
- Ensure sufficient gap between quotas and usage to accommodate failover
-
- Use highly available network connectivity for your workload public endpoints
- Provision Redundant Connectivity Between Private Networks in the Cloud and On-Premises Environments
- Ensure IP subnet allocation accounts for expansion and availability
- Prefer hub-and-spoke topologies over many-to-many mesh
- Enforce non-overlapping private IP address ranges in all private address spaces where they are connected
-
- Monitor end-to-end tracing of requests through your system
- Conduct reviews regularly
- Analytics
- Automate responses (Real-time processing and alarming)
- Send notifications (Real-time processing and alarming)
- Define and calculate metrics (Aggregation)
- Monitor End-to-End Tracing of Requests Through Your System
- Define and calculate metrics
- Send notifications
- Automate responses
-
- Monitor all components of the workload to detect failures
- Fail over to healthy resources
- Automate healing on all layers
- Rely on the data plane and not the control plane during recovery
- Use static stability to prevent bimodal behavior
- Send notifications when events impact availability
- Architect your product to meet availability targets and uptime service level agreements (SLAs)
-
-
Cost Optimization
-
- Establish ownership of cost optimization
- Establish a partnership between finance and technology
- Establish cloud budgets and forecasts
- Implement cost awareness in your organizational processes
- Monitor cost proactively
- Keep up-to-date with new service releases
- Quantify business value from cost optimization
- Report and notify on cost optimization
- Create a cost-aware culture
-
- Perform cost analysis for different usage over time
- Analyze all components of this workload
- Perform a thorough analysis of each component
- Select components of this workload to optimize cost in line with organization priorities
- Perform cost analysis for different usage over time
- Select software with cost effective licensing
-
-
Performance
-
- Learn about and understand available cloud services and features
- Evaluate how trade-offs impact customers and architecture efficiency
- Use guidance from your cloud provider or an appropriate partner to learn about architecture patterns and best practices
- Factor cost into architectural decisions
- Use policies and reference architectures
- Use benchmarking to drive architectural decisions
- Use a data-driven approach for architectural choices
-
- Use purpose-built data store that best support your data access and storage requirements
- Collect and record data store performance metrics
- Evaluate available configuration options for data store
- Implement Strategies to Improve Query Performance in Data Store
- Implement data access patterns that utilize caching
-
- Understand how networking impacts performance
- Evaluate available networking features
- Choose appropriate dedicated connectivity or VPN for your workload
- Use load balancing to distribute traffic across multiple resources
- Choose network protocols to improve performance
- Choose your workload's location based on network requirements
- Optimize network configuration based on metrics
-
- Establish key performance indicators (KPIs) to measure workload health and performance
- Use monitoring solutions to understand the areas where performance is most critical
- Define a process to improve workload performance
- Review metrics at regular intervals
- Load test your workload
- Use automation to proactively remediate performance-related issues
- Keep your workload and services up-to-date
-
-
Sustainability
-
- Scale workload infrastructure dynamically
- Align SLAs with sustainability goals
- Optimize geographic placement of workloads based on their networking requirements
- Stop the creation and maintenance of unused assets
- Optimize team member resources for activities performed
- Implement buffering or throttling to flatten the demand curve
-
- Optimize software and architecture for asynchronous and scheduled jobs
- Remove or refactor workload components with low or no use
- Optimize areas of code that consume the most time or resources
- Optimize impact on devices and equipment
- Use software patterns and architectures that best support data access and storage patterns
- Remove unneeded or redundant data
- Use technologies that support data access and storage patterns
- Use policies to manage the lifecycle of your datasets
- Use shared file systems or storage to access common data
- Back up data only when difficult to recreate
- Use elasticity and automation to expand block storage or file system
- Minimize data movement across networks
- Implement a data classification policy
- Remove unneeded or redundant data
-
- Articles coming soon
< All Topics
Print
Implement an account structure
PostedDecember 20, 2024
UpdatedMarch 21, 2025
ByKevin McCaffrey
Establishing a well-defined account structure is crucial for effective governance of cloud resource usage. It allows organizations to allocate costs more accurately, gain insights into spending patterns, and helps to enforce policies that ensure financial accountability as innovation continues.
Best Practices
Establish a Clear Account Structure
- Define a multi-account strategy that aligns with your organization’s business units or projects.
- Use AWS Organizations to create accounts for different departments, projects, or environments (e.g., production, development).
- Implement Service Control Policies (SCPs) to enforce governance over what actions can be performed within each account.
- Maintain a centralized billing account to aggregate costs, making it easier to track and manage expenses across all accounts.
- Regularly review and analyze account usage and costs to identify areas for cost savings and optimization.
Questions to ask your team
- How many AWS accounts does your organization currently have?
- Are there specific accounts designated for different teams or projects?
- How do you classify and label accounts to track expenses effectively?
- What policies are in place to govern the creation and deletion of accounts?
- How do you ensure that spending is tracked across all accounts in your organization?
- Are there automated tools in place to monitor costs across the account structure?
- How frequently do you review the account structure for cost allocation purposes?
- Do different departments have established budgets tied to their respective accounts?
- What measures are taken to prevent unauthorized account usage and the associated costs?
Who should be doing this?
Cloud Financial Manager
- Oversee the implementation of the account structure
- Develop policies for cost allocation and management
- Monitor compliance with budgeting and spending policies
- Provide training and resources on cost optimization practices
Cloud Architect
- Design the account structure to align with organizational objectives
- Ensure the architecture supports cost governance mechanisms
- Collaborate with stakeholders to implement the account structure effectively
DevOps Engineer
- Implement tools and processes for monitoring account usage
- Automate cost tracking and reporting mechanisms
- Maintain infrastructure in accordance with cost optimization policies
Finance Analyst
- Analyze cost data from various accounts
- Report on budget variances and optimization opportunities
- Work with teams to refine cost management strategies
Compliance Officer
- Ensure adherence to financial governance policies
- Conduct regular audits of account usage and spending
- Recommend adjustments to policies based on compliance findings
What evidence shows this is happening in your organization?
- Account Structure Policy Template: A template for creating an Account Structure Policy that outlines roles, responsibilities, and guidelines for account creation and management aligned with organizational goals.
- Cost Allocation Report: A detailed report that provides insights into cost allocations across different accounts and departments, highlighting usage patterns and opportunities for optimization.
- Account Management Checklist: A checklist to ensure all necessary steps are taken when creating and managing AWS accounts in line with the organization’s cost governance policies.
- Cost Optimization Dashboard: An interactive dashboard that visualizes account usage and costs across the organization, enabling stakeholders to monitor and manage expenditure effectively.
- Account Structure Strategy Guide: A guide that outlines strategies for structuring AWS accounts to optimize costs, improve governance, and enhance visibility across organizational units.
Cloud Services
AWS
- AWS Organizations: AWS Organizations allows you to create and manage multiple AWS accounts, helping you to structure your accounts for cost allocation and governance.
- AWS Budgets: AWS Budgets enables you to set custom cost and usage budgets that alert you when your usage exceeds thresholds, helping to manage costs effectively.
- AWS Cost Explorer: AWS Cost Explorer provides detailed insights into your AWS spending, allowing you to analyze and optimize costs as your account structure evolves.
Azure
- Azure Management Groups: Azure Management Groups allow you to manage multiple Azure subscriptions in a hierarchical structure, facilitating cost management across your organization.
- Azure Cost Management + Billing: This service helps you analyze your Azure spending and provides budgeting capabilities to ensure you stay within financial limits.
- Azure Advisor: Azure Advisor analyzes your deployments and provides recommendations to help you reduce costs and optimize resources based on your usage patterns.
Google Cloud Platform
- Google Cloud Billing: Google Cloud Billing allows you to create budgets and monitor your spending, ensuring that you can track costs across multiple projects and resources.
- Resource Hierarchy: The resource hierarchy in Google Cloud allows you to organize projects and resources in a way that assists with cost allocation and governance.
- Cloud Cost Management: Cloud Cost Management provides tools and insights to analyze and optimize spending across Google Cloud services.
Question: How do you govern usage?
Pillar: Cost Optimization (Code: COST)
Table of Contents