AWS Best Practices for Cost-Effective Resources and Optimization
Continue our overview of AWS Cost Optimization best practices by looking at best practices that cover resources and their optimization.
We'll cover the following...
Cost-effective resources
AWS Cost Optimization best practices continue by advising us to think holistically when choosing the resources for our landscapes.
COST 5: How do you evaluate cost when you select services?
Many different cost components can go into the total cost of ownership. This question is asking us to consider how we account for those things.
COST05-BP01 Identify organization requirements for cost: This best practice encourages customers to gather all their stakeholders and objectives for the cloud and then prioritize by the respective Well-Architected Pillar. Essentially, this just means figuring out what our trade-offs might be as we balance the cost equation.
COST05-BP02 Analyze all components of the workload: In another fairly obvious (but sometimes overlooked) step, this best practice says we should consider all our workloads.
COST05-BP03 Perform a thorough analysis of each component: When analyzing each part of our landscape or planned architecture, we need to be sure to view each aspect from all angles, including reliability, security, supportability, redundancy, and cost. We want a full spectrum of perspectives.
COST05-BP04 Select software with cost-effective licensing: When we have the option, open-source software may provide a less costly alternative. AWS offers many open-source offerings. Additionally, AWS recommends seeking out licensing plans that are outcome-based, as opposed to per-user or per-CPU-based.
COST05-BP05 Select components of this workload to optimize cost in line with organization priorities: Remember when we generated our priorities and needs list back in COST05-BP01, COST05-BP02, and COST05-BP03? Now, we can decide which AWS components and variants best match up with those priorities and needs.
COST05-BP06 Perform cost ...