After applying user-defined tags to resources, the company cannot yet filter by those tags in the AWS Cost Explorer console 20 days later. Why can't the tags be used for Cost Explorer filtering?

User-defined tags must be explicitly activated for cost allocation in the AWS Billing and Cost Management console before they can be used to filter costs in Cost Explorer. This activation process allows AWS to process and categorize your billing data based on these tags. It's not a matter of waiting a set number of days; rather, it's a configuration step. While an AWS Cost and Usage Report (CUR) provides detailed billing data, its creation isn't a prerequisite for tag-based filtering in Cost Explorer. Similarly, configuring a usage budget in AWS Budgets is for monitoring spending against thresholds, not for enabling tag-based cost analysis.