- 最新
- 投票最多
- 评论最多
It appears that the i3.2xlarge instances are not properly associating the "customer:value3" tag for cost allocation purposes, even though the tag is correctly applied to the instances and visible in other tools.
- Check that the "customer" tag is enabled for cost allocation in the Billing and Cost Management console under "Cost allocation tags".
- Verify the tag is correctly formatted as "customer" with a value of "value3". Ensure there are no extra spaces or special characters.
- Wait 24-48 hours and check the cost allocation again. There can sometimes be a delay before tags are fully processed for cost reporting.
https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/activate-built-in-tags.html
Okay, so we are using Reserved Instances and I have come to a conclusion that these costs cannot be filtered with User-defined cost allocation tags. I noticed this when I grouped by Usage type, the "missing resources" are listed as HeavyUsage:instance.type and this is related to Reserved Instances. Sadly this makes using the tags on Cost Explorer a bit harder as one needs to keep track on RIs separately.
Thanks for providing the screen shots and details. Could you run command "aws ec2 describe-instances --instance-id <instance-id>" on both the instances g5.xlarge and i3.2xlarge. If there is any difference in Tags related configuration between the two instances (example: PropagateTagsToVolumeOnCreation). If there is no difference, please open support ticket for further investigation.
Could not find any tagging related differences in the instances. Added the information regarding this attempt to the question.
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
I added some screenshots to the question to back up my claim a bit.