top of page

AWS cost allocation tags

AWS provides two types of cost allocation tags: AWS-generated tags and user-defined tags. Cost allocation tags can be used to organize resource costs on cost allocation reports.

Supported AWS cost allocation tags

Availability

Tag keys and values are case sensitive.

 

User-defined tags

The tags below have been activated as cost allocation tags. If you create these tags in your environment, you can use them as filters in the Cloud Analytics reports.

Alias

alias

Billing

billing

Env

env

Environment

environment

Name

Owner

owner

Product

product

Project

project

team

Team

unit

Unit

app.kubernetes.io/instance

app.kubernetes.io/managed-by

app.kubernetes.io/name

glue_job kubernetes.io/cluster-name

kubernetes.io/cluster/

kubernetes.io/created-for/pv/name

kubernetes.io/created-for/pvc/name

kubernetes.io/created-for/pvc/namespace

kubernetes.io/service-name

service-name

AWS-generated tags

aws:autoscaling:groupName

aws:backup:source-resource

aws:cloud9:environment

aws:cloud9:owner

aws:cloudformation:logical-id

aws:cloudformation:stack-id

aws:cloudformation:stack-name

aws:createdBy

aws:dlm:expirationTime

aws:dlm:lifecycle-policy-id

aws:dlm:lifecycle-schedule-name

aws:ec2:fleet-id

aws:ec2launchtemplate:id

aws:ec2launchtemplate:version

aws:ec2spot:fleet-request-id

aws:ecs:clusterName

aws:ecs:serviceName

aws:eks:cluster-name

aws:elasticfilesystem:default-backup

aws:elasticmapreduce:editor-id

aws:elasticmapreduce:instance-group-role

aws:elasticmapreduce:job-flow-id

aws:servicecatalog:portfolioArn

aws:servicecatalog:productArn aws:servicecatalog:provisioningPrincipalArn

aws:servicecatalog:source

aws:ssmmessages:session-id

aws:ssmmessages:target-id

aws:transfer:customHostname

aws:transfer:route53HostedZoneId

aws:zocalo:alias

2

Custom allocation tags

Ideally, you will be using the supported tags to track your AWS costs.

If you need a cost allocation tag that is not on the lists above, please open a support ticket.

Reactivate custom cost allocation tags

If you invite an existing AWS account into Dcode.tech, make sure to open a support ticket with the list of custom tags that you want to continue using.

We'll reactivate the cost allocation tags previously activated for that account.

Note

AWS cost allocation tags are managed at the payer account level. When an account moves to another organization, both user-defined and AWS-generated cost allocation tags previously activated for that account lose their "active" status and need to be activated again.

3

Limitations

It's important to understand the limitations from both AWS and the Dcode.tech Platform.

AWS restrictions

In particular, be aware that:

  • You can't backdate the application of a tag. Tags only start appearing on your cost allocation report after you apply them.

  • All tags can take up to 24 hours to appear in the AWS Billing and Cost Management console.

DoiT Platform restrictions

  • After you activate a cost allocation tag from the AWS organization and the tag appears in AWS billing data, it may take 6–8 hours for the DoiT Platform to fully process the billing data before the tags show up in the Analytics reports.

  • It may take up to 24 hours for a new tag to become available in the Analytics filters.

Get in Touch

This is a Paragraph. Click on "Edit Text" or double click on the text box to start editing the content.

bottom of page