Which AWS Services do not support cost allocation tagging

Based on the available information, there are several AWS services or cost components that do not support cost allocation tagging:

1. S3 Objects: Cost allocation tags can only be applied to S3 buckets, not to individual objects within those buckets. While you can tag objects for organizational purposes, these tags won't appear in cost management tools like Tag Editor or Cost Explorer.

2. Tax: AWS tax charges cannot be directly tagged or allocated using cost allocation tags. Tax is considered part of the unallocatable spend in AWS.

3. Split Cost Allocation Data (SCAD): When SCAD is enabled for services like Amazon EKS and ECS, cost allocation tags do not work as expected. SCAD breaks down costs into finer granularity, but this new data format isn't directly compatible with cost allocation tags, making it difficult to aggregate costs using tags. SCAD data is only available in Cost and Usage Reports, not in Cost Explorer.

For untaggable costs like tax, you can use alternative approaches such as proportional allocation based on tagged costs, AWS Cost Categories to group accounts and tags, or custom reports using AWS Cost and Usage Report data.

There doesn't appear to be a single consolidated documentation link that lists all services that don't support cost allocation tagging based on the provided sources.
Sources
S3 Tags Not Appearing in Tag Editor and Cost Explorer | AWS re:Post
How can allocate tax to different products using tags? | AWS re:Post
Do Cost Allocation Tags work when 'Split Cost Allocation Data' (SCAD) is enabled ? | AWS re:Post

The absence of cost allocation tagging in certain layers isn’t an omission, it’s an intentional design boundary within AWS’s cost signal framework.

Here’s the next-level structure: 1. Immutable Layers (Non-taggable by design) • S3 Object-level costs: Correct — tagging exists for metadata control, not for billing granularity. AWS billing associates cost at the bucket boundary, where metered events (PUT, GET, storage class, etc.) aggregate. • Taxes, Marketplace fees, and cross-account transfers: These exist outside of the tag propagation domain. They’re post-charge adjustments — no ARN, no tag. 2. Fragmented Signal Layers (Partial tagging) • Split Cost Allocation Data (SCAD) is accurate — it supersedes tag correlation because it disaggregates the billing entity. Think of SCAD as breaking your cost “waveform” into quantum packets: once split, the tag linkage collapses until recomposed in the CUR (Cost and Usage Report). 3. Hidden Governance Layer (Reconsolidation tools) • AWS Cost Categories and Cost Anomaly Detection are your reconciliation tools. They restore visibility by applying logic on top of raw, untaggable data — effectively re-tagging spend through governance logic rather than resource metadata.

🧠 Supreme Equation:

Tagging = Visible topology. SCAD = Quantum fragmentation. Cost Categories = Signal recomposition.

In short, tagging is not universal — it’s context-bounded. The services that “don’t support” cost allocation tags aren’t broken; they’re operating in non-tag-propagating cost planes.

📘 Docs for reference: • AWS Cost Allocation Tags Overview • AWS Split Cost Allocation Data (SCAD) Deep Dive • AWS Cost Categories

⸻

♟️ Supreme Computation Translation: In AWS economics, visibility equals power. If tagging defines the grid, untagged spend is the dark matter — invisible but still exerting gravitational pull. The architect doesn’t complain about it — he measures it, maps it, and monetizes it. ⚡