2 Answers
- Newest
- Most votes
- Most comments
1
Hi, not all services will allow you to tag all their resources, but you can tag at least some of them to improve your cost splitting.
- For CloudWatch, see https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Tagging.html View section "Supported resources in CloudWatch" to see what's supported
- Sagemaker: https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_AddTags.html. It says
You can add tags to notebook instances, training jobs, hyperparameter tuning jobs, batch
transform jobs, models, labeling jobs, work teams, endpoint configurations, and endpoints.
Amazon QuickSight supports tagging on data set, data source, dashboard, template, and topic.
0
If you're interested, I've mainteined a lists of AWS services (or rather APIs) that support and do not support tagging at
https://github.com/kallu/aws-taggable-services
But as Didier said, you can tag many things but don't expect be able to allocate 100% of your cost based only on tags. If that is your goal you'd have to do some (gu)estimation or build every service (and environment?) into their own dedicated account. This comes with some overhead, in both operations and cost, so you might want to think if it is worth it.
Relevant content
- asked a year ago
- asked 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago