- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
There may be a few reasons why you may be getting charged for VPC even if you are not using it. Here is a glimpse of them.
AWS started charging for public IPv4 addresses from February 2022. Even if you are not explicitly using public IPs from VPC, background services like EC2 metadata service could be using a public IP address behind the scenes.
Check if you have any
network interfaces
or
elastic network interfaces
provisioned in your account. These will be associated with a VPC and incur charges.
Review your security groups and NAT gateways associated with VPC. Even if resources using them are in the free tier, the networking components themselves will attract charges.
Check your billing reports for the services tagged under
VPC
like
Route Tables
,
Internet Gateways
etc. Even if these resources are inactive, you may be charged for maintaining them.
Any of the vpc is not attached to any other services , because Iam not using any of the other services rather than ec2 instance .and I didn’t attach vpc to ec2 or any other And Iam not running any ec2 instance or any other services since 4 days but I was charged it showed mainly vpc Iam not understanding what would be the reason
Use cost explorer to drill down cost details: https://docs.aws.amazon.com/cost-management/latest/userguide/ce-what-is.html
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa