Skip to content

Update cloud-cost-management-faqs.md #11291

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 18, 2025
Merged

Update cloud-cost-management-faqs.md #11291

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
aa48b16
Update cloud-cost-management-faqs.md
joeyouss Aug 18, 2025
5545893
Update cloud-cost-management-faqs.md
joeyouss Aug 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions kb/cloud-cost-management/cloud-cost-management-faqs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -227,6 +227,9 @@ You can set up perspectives/folders for each of those and then limit access to t

## Recommendations

## How are recommendation savings calculated for each type of recommendation?
For nodepool, ECS, workload recommendations, savings are calculated based on on-demand prices. All savings estimates are standardized on on-demand pricing to ensure consistency across recommendations.

### We have found that some AWS EC2 instances are still visible in recommendations list even they are stopped before 2-3 days ago. is it the usual behavior for stopped ec2s?

Yes, this can happen if the stop action wasn't captured during the next sync cycle after the recommendation was made. In such cases, the recommendation disappears because the instance is no longer in a running state.
Expand Down