How to Troubleshoot AWS Billing Issues
Analyzing AWS Billing Issues
If you’re running software on AWS, then each month you’ll end up troubleshooting AWS billing issues.
This last month, my AWS bill for one of our internal accounts was higher than expected. Surprise, surprise!
I started to investigate the issues by navigating to my previous months bill from the Billing & Cost Management Dashboard by selecting the Bills section of the menu, highlighted in red.
To start this process on your own AWS account, click here.
CloudWatch AWS billing issues
To disable the CloudWatch monitoring, I can follow the instructions to Enable CloudWatch monitoring here, and turn off CloudWatch.
To start, I’ll open a new tab to display the AWS EC2 instances in Oregon by clicking on Service from the navigation bar, and then right mouse clicking on EC2, and opening this url in a new browser tab.
The EC2 region will display. I’ll want to ensure that I’m pointing to the right region, Oregon, highlighted in orange. Next, I’ll click on the Running Instances 1 highlighted in red.
DynamoDB AWS billing issues
In the previous section, we deleted the micro EC2 instance, but have we deleted everything? A quick trip to the VPC dashboard, shows that we have 2 NAT Gateways still up and running.
Are we being charged for these? It’s probably not worth the risk, so we’ll delete them.
We also notice that we’re being bill for an ELB. On the EC2 Instances view, scroll down to the Elastic Load Balancing section to delete the ELB.
We’re using Amazon’s Elastic Container Service for Kubernetes (K8S). I believe that we’ve already blown the EKS way, so we’ll confirm.
Skipping ahead, we notice that we have a t2.medium MySQL RDS instance that is still running. We’ll blow this away as well.
Last, but not least, AWS is charging us for a number of Hosted Zones. These Hosted Zones were leveraged by our Kubernetes setup.
We’ll navigate to Route 53 to blow away these Hosted Zones for US-West-2. Deleting Hosted Zones via the Admin interface is painful as you can only single select.
At this point, we’ve hopefully cleaned up our problematic Oregon (US-West) zone. Continue to go through your other problems and check back in during every billing period.