- Newest
- Most votes
- Most comments
Based on the information you've provided, it appears that you're experiencing a discrepancy between your EC2 instance usage and billing. This situation can occur for a few reasons:
-
Terminated instances: Even after terminating EC2 instances, they may still appear on your bill for the current billing period. AWS charges for the time the instances were running, even if they're no longer active.
-
Delayed termination: Sometimes, instances can get stuck in the "shutting-down" state. In this case, you might continue to incur charges until the termination process completes.
-
DataBricks integration: Since you mentioned using DataBricks, it's possible that the DataBricks service is managing EC2 instances on your behalf, and these might not be visible in your regular EC2 console view.
To address this issue:
-
Double-check your EC2 console for any instances in non-terminated states, including "stopping" or "shutting-down".
-
Review your DataBricks account and ensure all clusters are properly shut down.
-
Check your AWS Cost Explorer for more detailed information about the charges, including the specific resources and time periods involved.
-
If you still can't locate the source of the charges, it's recommended to contact AWS Support directly. While there isn't a direct email, you can open a support case through the AWS Support Center in your AWS Management Console.
Remember, you're only charged for instance usage when an instance is in the "running" state. Once an instance is terminated, you should stop incurring charges for that instance. However, you may still see charges for the period when the instance was active.
Sources
Troubleshoot Amazon EC2 instance stop issues - Amazon Elastic Compute Cloud
Terminate Amazon EC2 instances - Amazon Elastic Compute Cloud
Troubleshoot Amazon EC2 instance termination issues - Amazon Elastic Compute Cloud
How EC2 instance stop and start works - Amazon Elastic Compute Cloud
Hi, l
ooking at your screenshot, you still have some billable resources like NAT gateways, Elastic IPs, etc. Delete them (if appropriate) to take care of the "no type" at least.
Didier
Relevant content
- asked a year ago
- asked 4 months ago
- asked 4 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 days ago
- AWS OFFICIALUpdated 4 years ago