In our latest blog post on investigating AWS bill issues, we explored issues with CloudWatch and EC2. At the end, we terminated an EC2 instance.
The next item on our bill for November 2019 is the DocumentDB.
DocumentDB is Amazon’s version of MongoDB. We use DocumentDB to store unstructured data in a JSON format. In November of 2019, our DocumentDB bill was entirely out of US West (Oregon), which is one of the areas that we should no longer be billed for. A quick glance at our DocumentDB in US West (Oregon) displays that we should no longer be charged for DocumentDB in December of 2019.
The next big ticket item are our EC2 Instances. For November 2019, more than 50% of the spend was on EC2 instances.
In our previous post, 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. I’ll check back in at the end of the month to see how we did.