- Newest
- Most votes
- Most comments
Your EC2 instance needs the VPC where it is, but you won't be able to delete the VPC or the subnets it contains while there are EC2 instances or anything else with network interfaces within them. When you click the Delete button in the console, it will tell you if there are dependencies on the VPC and provides a list of them.
The VPC itself doesn't cost anything, so you don't need to worry about it existing from a cost perspective. Only resources inside the VPC, such as your EC2 instance, incur costs related to the VPC, such as data transfer fees, whose amounts depend on how much data is transferred and to where (e.g., between availability zones, between regions, or to the public internet).
I still suggest you use Cost Explorer to obtain a breakdown of your costs. It's an easy-to-use graphical console where you can first filter your costs by "Service" being VPC and then having the graph broken down by "Usage Type", which breaks down the VPC costs into smaller constituent parts, such as cross-AZ traffic fees, internet traffic, public IP address usage, and so on.
On another note, you can use the Global View in the EC2 console to see a summary of all the VPCs, subnets, and associated resources you have across all AWS regions. All enabled regions have a default VPC by default.
Hi,
I would suggest you to see if you have a default VPC configured in your region
If yes, this VPC has a bunch of default components : see https://docs.aws.amazon.com/vpc/latest/userguide/default-vpc-components.html
Some of them are even automatically created by AWS on your behalf: see Note on page. Those components may be the source of billing that you see. To avoid such issue, you must get rid of default VPC.
Best,
Didier
I do have a VPC which is what recently appeared automatically a few days ago. Im not sure how to get rid of it though. I can see it in VPCs but the only action available is to delete it. What if it messes up my EC2 instance which hosts my ERP? Is there no way to STOP it or DISABLE it and see if it wont cause undesired results first?
Cost Explorer is usually a good tool for drilling down into where costs originate, but assuming you've checked that no public IPs are configured on ENIs in your VPC(s), a couple of other typical examples where public IPs can exist without showing in the ENI list include site-to-site VPNs and Global Accelerator endpoints that can be enabled for ALBs, NLBs, or EC2 instances.
Relevant content
- Accepted Answerasked 6 months ago
AWS OFFICIALUpdated 10 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
I did and I can see that VPC is the only new cost over the past 5 months. Thats how I knew the cost was related to the VPC service. I filtered VPC and selected Usage type ALL and I now instead of just the bar for the current month marked as VPC, I get bars for every month since I started the service back in March. March 744 hrs, April 720 hrs, May 744 hrs, June 720 hrs, July 744 hrs and August 744 hrs. Not sure what that meanns.
I went to the Global View on EC2 and i seem to have 17 regions (dunno why), 17 VPCs in 17 regiones, 55 subnets, 19 security groups and 134 prefix lists! Oh my! No clue what all those things mean
On the right-hand side in Cost Explorer, above the "Filters" section, there's a "Group by" / "Dimension" selection. If you set that to "Usage Type" after filtering on the VPC "Service", you'll see the breakdown of the VPC costs by individual usage type. If the "Group by" selection is set to "Service" with the filter set to include only one service, the graph and table won't show a breakdown but only the total sum for the whole service.
The 17 regions you're seeing are the older regions that are enabled by default. Newer ones are opt-in. Every enabled region has a default VPC provisioned automatically by AWS, but if the "network interfaces" count in the region is 0, then you have no resources in the VPC and you can simply switch to the region, open the VPC console, select your VPC, and click Delete. The console will take care of deleting all the related subnets and security groups for you before deleting the VPC.