- 新しい順
- 投票が多い順
- コメントが多い順
I would start by using Cost Explorer and filtering for your tag = no-tag. This will limit the costs and usage shown to only things that don't have the tag you are researching. Then, you can group by useful things like service, region, usage-type to narrow down where and possibly what is causing the usage/cost that is not tagged.
Understand, that things like Data Transfer cannot be tagged, so you will never be able to tag 100% of your costs.
Once you have the non-tagged service and region and possibly usage types, then you can either look in Cost and Usage Reports or possibly search in the AWS Tag Editor to find specific resources that are not tagged.
If you are looking to do this over the long term and/or automate, then you should checkout the various options including pros and cons in this AWS Whitepaper Tagging Best Practices
Yes, you can use Tag Editor from your console to identify those that are not tagging/not tagged with values
関連するコンテンツ
- AWS公式更新しました 3年前
- AWS公式更新しました 1年前
- AWS公式更新しました 1年前