1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
The subject and body appear to be asking 2 different questions. I assume you're interested in knowing why RDS:ChargedBackupUsage is untagged. I am aware of 2 possible cases: 1/ orphaned snapshots have no DB instance to refer to, hence no reference to instance tags either. In Cost Explorer and Cost and Usage Report, costs for RDS orphaned snapshots aggregated in a single, untagged item. 2/ Short-lived instances (less than one hour) might not get time to export tags. As a result, tags might not get applied to snapshots of short-lived instances.
If you have an AWS support option, I recommend opening a support case and support engineer can look into your AWS account and help trace those untagged charges back to specific snapshots / instances.
répondu il y a 2 mois
Contenus pertinents
- demandé il y a 6 mois
- Réponse acceptéedemandé il y a un an
- demandé il y a un an
- demandé il y a un mois
- AWS OFFICIELA mis à jour il y a 2 ans
Please fix the Subj vs Body discrepancies.