- Le plus récent
- Le plus de votes
- La plupart des commentaires
- Go to Cost Explorer -> Choose Date Range in right pane
- Granularity -> Daily
- Dimension -> Usage Type
- Service -> AWS Mainframe Modernization
Note: Repeat same by changing option in Dimensions field as Cost Category, Availability zone and Charge Type one by one and see where you see charges.
This would show you when and what are the resources/which AZ that's happening.
If you want to setup alert, you can consider setting up AWS budgets and configure alarm on those, which would notify you, if you cross the defined usage threshold. Follow the Well Architected Lab instructions here for setting up budget alert based on your usage.
However, if you still don't figure out and think that it's not a legitimate charge, contact AWS Billing Support Team by following instructions at here
Hope you find this helpful.
Comment here if you have additional questions, happy to help.
Abhishek
If there is any AWS Mainframe Modernization Environment created under your account, you will the charges for EC2 instances running under the managed environment. Those instances will not be visible under EC2 console.
For more details on the pricing for AWS Mainframe Modernization service please visit - https://aws.amazon.com/mainframe-modernization/pricing/?nc=sn&loc=3&refid=50fb4519-c1dd-4ebb-8b05-f83e58d8e14b.
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 ans
- demandé il y a 7 mois
AWS OFFICIELA mis à jour il y a 2 ans
Thanks that was a very helpful answer but I am still confused; I ran the report and downloaded and it looks like I am being charged for an M5 instance starting on 7/31 but I don't see any instances running; can you help, given this chart? Where do I see if an instance is running? I don't see any running
Thanks
Usage type USE2-m5.largeBluAgeRuntime($) USE2-m5.largeBluAgeRuntime-Free($) Total costs($) 8/1/2023 7.44 7.44 8/2/2023 7.44 7.44 8/3/2023 7.44 7.44 8/4/2023 2.17 2.17
I'm really sorry for delayed response and hope you'd have figured out by now. Are you sure there is no mainframe modernization application is running. It seems this charge is in us-east-2(Ohio) region, so make sure you are checking in us-east-2 region. Also can you do the same exercise with service EC2, and see where is that instance cost coming from.