Skip to content

Commit

Permalink
Update view-your-savings.md (#5085)
Browse files Browse the repository at this point in the history
  • Loading branch information
elinornetapp authored Nov 28, 2024
1 parent 34d960c commit ee6043a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/docs/eco/tutorials/view-your-savings.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ The Overview dashboard includes a summary line of: 
* **Total Saved**: Total amount saved as a result of reserved instance and savings plan coverage. 
* **Current Commitment**: The amount currently committed to reserved instances. The lower the commitment, the more flexible and dynamic the account's compute resources can be. 
* **MTD Savings**: Total generated savings from the first day of the month to the most recent update. 
* **EC2 ESR**: Effective Savings Rate (ESR) is the average savings across an entire compute usage. The calculation for Effective Savings Rate (ESR) is [Net Savings]/[On-Demand Cost Equivalent]. Net Savings include the total savings achieved subtracted from the cost of unused commitments. This displays the ESR for EC2, ECS/ Fargate, EKS, and Lambda, excluding Spot instances.
* **EC2 [ESR](eco/tutorials/view-your-savings?id=esr-effective-savings-rate-chart)**: Effective Savings Rate (ESR) is the average savings across an entire compute usage. The calculation for Effective Savings Rate (ESR) is [Net Savings]/[On-Demand Cost Equivalent]. Net Savings include the total savings achieved subtracted from the cost of unused commitments. This displays the ESR for EC2, ECS/ Fargate, EKS, and Lambda, excluding Spot instances.
* **Non-EC2 ESR**: The AWS services considered are RDS, Redshift, ElastiCache, and OpenSearch. 
* **EC2 ESR with Spot**: The AWS services considered are all EC2 usage (including spot usage) plus other services that can be covered by a compute savings plan: EC2, ECS/Fargate, EKS, and Lambda. 

Expand Down

0 comments on commit ee6043a

Please sign in to comment.