1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
4
To break down the charges, I'd suggest you to:
Go to Cost Explorer -> Choose Date Range in right pane
Granularity -> Daily
Dimension -> Usage Type
Service -> VPC
Repeat same by changing the Dimension from Usage Type to API Operation, Availability Zone, Region, this would help you drill down further and understand, where the charge is coming from.
For more details, refer AWS VPC FAQs. While you do your dev work, it's very obvious that you must be using AWS VPC for that period of time, so AWS VPC would still incur charge for some of that usage, when your resources were turned on. For example EC2 instance ENI, Public IP addresses, RunInstance APIs etc.
Hope it helps, comment here if you have additional questions.
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 4 meses
- OFICIAL DE AWSActualizada hace 2 años
Glad you figured out.
Super useful, thanks so much! Turns out I'm burning "CAN1-VpcEndpoint-Hours", so I guess my SSM endpoints are what's driving the costs. I should have clarified - the more basic cost reports I was looking at were showing costs being >95% VPC.