- Newest
- Most votes
- Most comments
Hi,
So sorry for any concern this has caused. I've passed along your request to our teams. Continue to monitor your case for updates: go.aws/account-support.
- Sage A.
I understand you have a support case regarding an unexpected charge from an idle SageMaker endpoint. For assistance with your existing case, I recommend visiting the AWS Support Center at https://console.aws.amazon.com/support/ where you can add correspondence directly to your case or check its current status.
Regarding SageMaker endpoint charges, it's important to note that endpoints incur charges based on the instance type and the duration they remain deployed, regardless of whether they're actively processing inference requests. Even idle endpoints continue to accrue costs because the underlying compute resources remain provisioned and available. To avoid ongoing charges, endpoints must be deleted, which you've indicated you've already done.
If you're looking for faster response times on support cases, you may also want to review your AWS Support plan options, as different support tiers offer varying response time commitments. You can manage your support interactions and add any additional details about the deleted endpoint through the AWS Support Center.
answered a month ago
Relevant content
asked a month ago
- AWS OFFICIALUpdated 5 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 12 days ago

Thank you for the automated info. However, this question is specifically regarding an unassigned billing ticket (Case ID: ***************** opened Sep 2) requesting a one-time courtesy adjustment for an idle, now-deleted SageMaker endpoint. Could an AWS Support Community Manager please help route/flag this case to the internal billing queue? Thank you!"
Edit: Removed case ID — Sage A.