4 ms·
You can get cost breakdown on a more granular level by taking advantage of tagging. You can tag your resources logically and get a break down by tag. The bigge
by scarface74 6y ago
You can get cost breakdown on a more granular level by taking advantage of tagging. You can tag your resources logically and get a break down by tag.
The biggest mistake I see is that people jump into AWS whole hog without doing the research or if they are large enough, hiring someone who knows what they are doing.
https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2...
- mherrmann 6y agoI don't understand why I even need to do manual things such as "tagging" (besides learning what that even means in AWS) to find out something as simple as why I'm being charged as much as I'm being charged. I'm sorry. It's inexcusable.
- scarface74 6y agoAnd large organizations would complain about why they couldn’t group their resources like they want to. Having individual bucket costs would be of very little use for cost allocation and to tie back to something like a department. For instance, we tag every resource created with the same CloudFormation template with the same tag. We can get billing based on an “application” and all of its related resources. Just like AWS is not understandable to someone new, I feel the modern front end ecosystem is royal cluster but yet and still thousands of people understand it after a 12 week boot camp.
- mherrmann 6y agoYou could have both. Let advanced users tag. But give less sophisticated users insight into what they're being charged for - without having to go through a 12 week boot camp.