AWS Security ChangesHomeSearch

AWS compute-optimizer documentation change

Service: compute-optimizer · 2026-04-01 · Documentation low

File: compute-optimizer/latest/ug/savings-estimation-mode.md

Summary

Added detailed documentation about default savings estimation mode behavior, including Billing Transfer restrictions, default preferences based on account types, and overriding preferences

Security assessment

This change adds comprehensive documentation about billing and cost optimization features, but doesn't address security vulnerabilities or add security documentation. It's focused on cost management and service configuration.

Diff

diff --git a/compute-optimizer/latest/ug/savings-estimation-mode.md b/compute-optimizer/latest/ug/savings-estimation-mode.md
index f117dd00a..1c63dfaa1 100644
--- a//compute-optimizer/latest/ug/savings-estimation-mode.md
+++ b//compute-optimizer/latest/ug/savings-estimation-mode.md
@@ -5 +5 @@
-Next steps
+Default behaviorOverriding default preferencesNext steps
@@ -25,0 +26,27 @@ The savings estimation mode preference is only available for accounts within AWS
+###### Important
+
+When you use Billing Transfer as a bill source account, the `AfterDiscounts` functionality is disabled and you can't enable it. Bill source accounts must validate rightsizing recommendations against their Reserved Instance and Savings Plans inventory to consider any unused commitment before making optimization decisions.
+
+## Default behavior
+
+Compute Optimizer applies a default savings estimation mode based on your account type and Cost Optimization Hub enrollment status.
+
+When a management account opts in to Cost Optimization Hub, all member accounts in the organization automatically default to `AfterDiscounts`. This means Compute Optimizer uses your organization's pricing discounts, such as Savings Plans and Reserved Instances, when estimating potential cost savings. If the management account opts out of Cost Optimization Hub or disables savings estimation mode in Cost Optimization Hub, member accounts without an explicit preference revert to `BeforeDiscounts`.
+
+The following table describes the default behavior when no explicit savings estimation mode preference is set.
+
+Account type | Default savings estimation mode  
+---|---  
+Management account or Delegated Administrator | `AfterDiscounts` — Compute Optimizer uses pricing discounts in savings estimates.  
+Standalone account | `AfterDiscounts` — Compute Optimizer uses pricing discounts in savings estimates.  
+Member account (management account opted in to Cost Optimization Hub) | `AfterDiscounts` — Compute Optimizer uses pricing discounts in savings estimates.  
+Member account (management account not opted in to Cost Optimization Hub) | `BeforeDiscounts` — Compute Optimizer uses On-Demand pricing only.  
+  
+###### Note
+
+If you have Linked account discounts disabled in Cost Explorer, Compute Optimizer will be set to `BeforeDiscounts`.
+
+## Overriding default preferences
+
+You can override the default behavior by explicitly setting a savings estimation mode preference using the `PutRecommendationPreferences` API or the Compute Optimizer console. An explicit preference always takes precedence over the default behavior described above.
+
@@ -28 +55 @@ Only the account manager or delegated administrator of your organization can act
-If the savings estimation mode preference isn’t activated, Compute Optimizer only uses the default On-Demand pricing information.
+If the savings estimation mode preference isn't activated and the account doesn't qualify for a default of `AfterDiscounts`, Compute Optimizer uses the default On-Demand pricing information.