# Tagging AWS Elemental MediaConvert resources
TaggingUse integrated AWS tags on AWS Elemental MediaConvert resources

You can now use standard AWS tags with MediaConvert jobs the same way that you do with queues, templates, and presets. You can use these tags to sort your billing report for cost allocation purposes, to include your MediaConvert resources in resource groups with other AWS resources, and to control access to specific resources.Set up cost allocation reports to sort your AWS bill by the tags that you apply to AWS Elemental MediaConvert resources

You can use the tags you apply to AWS Elemental MediaConvert queues, job templates, and output presets as cost allocation tags. First activate them in the AWS Billing and Cost Management dashboard, and then set up a billing report to view your AWS charges by resource.Tagging AWS Elemental MediaConvert resources on the console

You can now work with tags on existing AWS Elemental MediaConvert queues, job templates, and output presets in the MediaConvert console.Use AWS Elemental MediaConvert tags for cost allocation through tagging

You can now activate tags on AWS Elemental MediaConvert queues, job templates, and output presets in the AWS Billing and Cost Management dashboard, and then set up a monthly cost allocation report.Tagging AWS Elemental MediaConvert resources initial release

You can now tag MediaConvert resources when you create them using the MediaConvert console, the MediaConvert API, or the AWS CLI. You can list the tags on an existing MediaConvert resource, and add and remove tags on existing MediaConvert resources, through the MediaConvert API and AWS CLI.

A *tag* is a label that you assign or that AWS assigns to an AWS resource. Each tag consists of a *key* and a *value*. For tags that you assign, you define the key and value. For example, you might define the key as "stage" and the value as "test." Tags help you to identify and organize your AWS resources. Tags that you assign to AWS Elemental MediaConvert jobs, job templates, queues, and presets are integrated with tags across AWS services.

Popular use cases for these tags are as follows:
+ You can activate these tags on the AWS Billing and Cost Management dashboard, and then set up a monthly cost allocation report. For more information, see [Setting up resources for cost allocation through tagging](setting-up-resources-for-catt.md).
+ You can allow or deny resource-level access to your resources using AWS Identity and Access Management (IAM). For more information, see [Controlling access to AWS resources using resource tags](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_tags.html) in the *IAM User Guide*.

**Topics**
+ [

# Setting up AWS Elemental MediaConvert resources for cost allocation through tagging
](setting-up-resources-for-catt.md)
+ [

# Adding tags when you create an AWS Elemental MediaConvert resource
](add-tags-on-create.md)
+ [

# Adding tags to an existing AWS Elemental MediaConvert resource
](add-tags-to-existing.md)
+ [

# Viewing tags on an AWS Elemental MediaConvert resource
](view-tags-on-resource.md)
+ [

# Editing tags on an AWS Elemental MediaConvert resource
](edit-tags-on-resource.md)
+ [

# Removing tags from an AWS Elemental MediaConvert resource
](remove-tags-from-resource.md)
+ [

# Restrictions for tags on AWS Elemental MediaConvert resources
](resource-tagging-restrictions.md)
+ [

# Using metadata tags with AWS Elemental MediaConvert jobs
](user-metadata-tags.md)

# Setting up AWS Elemental MediaConvert resources for cost allocation through tagging
Setting up resources for cost allocation through tagging

For all outputs that you produce using an on-demand queue, you can use the AWS Billing and Cost Management dashboard to set up a monthly cost allocation report. This report shows what AWS charges you for transcoding, sorted by resource. You can set up your jobs so that your job outputs are sorted by tags on the job or on a resource that you use to create the job. That is, you can sort your bill by the tags that you put on the job, on the queue that you submit the job to, on the job template that you create the job from, or on the output presets that you use to set up the individual outputs of the job.

**To set up cost allocation through tagging for your AWS Elemental MediaConvert charges**

1. Tag the resources that you intend to sort your bill by. For instructions, see the other topics in this chapter.

1. Create your transcoding jobs, specifying how you want your costs allocated as follows:

   1. On the **Create job** page, in the **Job** pane on the left, under **Job settings**, choose **AWS integration**.

   1. In the **Job settings** section on the right, under **AWS integration**, for **Billing tag source**, choose which tags you want to use to sort the job's outputs. You can choose to sort by tags on a resource that you use to create the job—job template, output preset, or queue. Or you can choose **Job** to sort by the tags on the job itself.
**Note**  
Jobs, and the tags on them, persist for only 90 days. If your workflow references tags over longer periods of time, use tags on the queue, job template, or output preset rather than tags on the job.

1. Activate these tags on the AWS Billing and Cost Management dashboard. For more information, see [Activating user-defined cost allocation tags](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/activating-tags.html) in the *Billing and Cost Management User Guide*.

1. Set up your report. For more information, see [Monthly cost allocation report](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/configurecostallocreport.html) in the *Billing and Cost Management User Guide*.

# Adding tags when you create an AWS Elemental MediaConvert resource
Adding tags when creating a resource

The following procedures show you how to add tags to your MediaConvert queues, job templates, and output presets when you create them.

**Topics**

## Adding tags when creating a resource (console)
Adding tags when creating a resource

You can add tags when you create a queue, job template, or output preset.

**To add tags when you create a queue, job template, or output preset (console)**

1. Follow the steps in one of the following procedures to begin creating the resource, but don't save the resource:
   + [Tutorial: Configuring job settings](setting-up-a-job.md)
   + [Creating a queue](creating-queues.md)
   + [Creating a template](creating-template-from-scratch.md)
   + [Creating a preset](creating-preset-from-scratch.md)
   + [Creating a preset, based on a system preset](create-custom-preset-from-system-preset.md)

1. Find the **Tags** section in the relevant location:
   + For jobs – on the **Create job** page, after you choose **Settings** from the **Job** section on the left
   + For queues – at the bottom of the **Create queue** page
   + For output presets – at the bottom of the **Create preset** page
   + For job templates – at the bottom of the **Create job template** page, after you choose **Settings** from the **Job** section on the left

1. In the **Tags** section, choose **Add**.

1. For **Tag key**, enter a name for the tag. For **Tag value**, enter a value for the tag.

1. Choose **Create** to save the new resource with its tags.

## Adding tags when creating a resource (API and AWS CLI)
Adding tags when creating a resource (API and AWS CLI)

When you create a job, job template, output preset, or queue using the AWS Elemental MediaConvert API or the AWS CLI, submit your JSON specification for the resource as usual. Include tags as shown in the following JSON example, in `tags`:

```
{
	"name": "Job Template Test with Resource Tags",
	"description": "Job Template Test",
	"tags":{
		"Company": "Banana",
		"Stage": "Production"		
	},
	"settings":{
```

# Adding tags to an existing AWS Elemental MediaConvert resource
Adding tags to an existing resource

The following procedure shows you how to add tags to existing job templates, output presets, or queues using the AWS Elemental MediaConvert console. You can't use the console to add tags to existing jobs.

For information about adding tags using the API, see the `POST` method in the [Tags](https://docs.aws.amazon.com/mediaconvert/latest/apireference/tags.html) endpoint section of the *MediaConvert API Reference*.

**Note**  
Tags on your MediaConvert resources don't appear in the JSON response to a `GET` request on the resource. Instead, send a `GET` request to the `Tags` endpoint. If you send your request directly to the API, rather than using an SDK, you must URL encode the resource ARN.

**To add tags to job templates, output presets, and queues (console)**

1. Open the MediaConvert console at [https://console.aws.amazon.com/mediaconvert](https://console.aws.amazon.com/mediaconvert).

1. Choose the three-bar icon on the left to access the left navigation pane.

1. Choose **Output presets**, **Job templates**, or **Queues**.

1. Choose the name of the specific resource that you want to add a tag to.

1. Choose the **Update**, **Edit queue**, or **Update preset** button in the upper right. 

1. In the **Tags** section at the bottom of the page, choose **Add**.

1. For **Tag key**, enter a name for the tag. For **Tag value**, enter a value for the tag.

1. Choose **Save**.

# Viewing tags on an AWS Elemental MediaConvert resource
Viewing tags on a resource

The following procedure shows you how to view tags on existing queues, job templates, and output presets using the AWS Elemental MediaConvert console.

To do this using the API, see the `GET` method in the [Tags arn](https://docs.aws.amazon.com/mediaconvert/latest/apireference/tags-arn.html) endpoint section of the *MediaConvert API Reference*. If you send your request directly to the API, rather than using an SDK, you must URL encode the resource ARN.

**To view tags for queues, job templates, and output presets (console)**

1. Open the MediaConvert console at [https://console.aws.amazon.com/mediaconvert](https://console.aws.amazon.com/mediaconvert).

1. Choose the three-bar icon on the left to access the left navigation pane.

1. Choose **Job templates**, **Output presets**, or **Queues**.

1. Choose the name of the specific resource that has tags that you want to view.

1. View the tags for the resource in the **Tags** section at the bottom of the page.

# Editing tags on an AWS Elemental MediaConvert resource
Editing tags on a resource

The following procedure shows you how to edit tags on existing job templates, output presets, and queues using the AWS Elemental MediaConvert console. You can't edit tags on existing jobs.

To do this using the API, see the `POST` method in the [Tags](https://docs.aws.amazon.com/mediaconvert/latest/apireference/tags.html) endpoint section of the *MediaConvert API Reference*.

**To edit tags for job templates, output presets, and queues (console)**

1. Open the MediaConvert console at [https://console.aws.amazon.com/mediaconvert](https://console.aws.amazon.com/mediaconvert).

1. Choose the three-bar icon on the left to access the left navigation pane.

1. Choose **Job templates**, **Output presets**, or **Queues**.

1. Choose the name of the specific resource that has tags that you want to change.

1. Choose the **Update**, **Edit queue**, or **Update preset** button in the upper right. 

1. In the **Tags** section at the bottom of the page, edit any values for **Tag key** and **Tag values** that you want to change.

1. Choose **Save**.

# Removing tags from an AWS Elemental MediaConvert resource
Removing tags from a resource

The following procedure shows you how to remove tags from existing job templates, output presets, and queues using the AWS Elemental MediaConvert console.

To do this using the API, see the `PUT` method in the [Tags](https://docs.aws.amazon.com/mediaconvert/latest/apireference/tags.html) endpoint section of the *MediaConvert API Reference*.

**To remove tags from a job template, output preset, or queue (console)**

1. Open the MediaConvert console at [https://console.aws.amazon.com/mediaconvert](https://console.aws.amazon.com/mediaconvert).

1. Choose the three-bar icon on the left to access the left navigation pane.

1. Choose **Job templates**, **Output presets**, or **Queues**.

1. Choose the name of the specific resource that has tags that you want to change.

1. Choose the **Update**, **Edit queue**, or **Update preset** button in the upper right. 

1. Next to any tag that you want to delete, choose **Remove**.

1. Choose **Save**.

# Restrictions for tags on AWS Elemental MediaConvert resources
Tag restrictions

The following basic restrictions apply to tags:
+ Maximum number of tags per resource – 50.
+ Maximum **Key** length – 128 Unicode characters.
+ Maximum **Value** length – 256 Unicode characters.
+ Valid values for **Key** and **Value** – Uppercase and lowercase letters in the UTF-8 character set, numbers, space, and the following characters: \$1 . : / = \$1 - and @.
+ Tag keys and values are case sensitive.
+ Don't use the `aws:` prefix for either keys or values. It's reserved for AWS use.

# Using metadata tags with AWS Elemental MediaConvert jobs
Using metadata tags

Unless you have existing integrations or workflows that rely on metadata (`userMetadata`) tags, we recommend that you use standard AWS tags for both automatic integration with AWS services and for custom integrations and workflows. For more information, see [Tagging AWS Elemental MediaConvert resources](tagging-mediaconvert-resources.md).

A *tag* is a label that you assign or that AWS assigns to an AWS resource. Each tag consists of a *key* and a *value*. For tags that you assign, you define the key and value. For example, you might define the key as "stage" and the value as "test." Tags help you to identify and organize your AWS resources. Metadata tags that you assign to AWS Elemental MediaConvert jobs appear in Amazon EventBridge notifications.

You add metadata tags to jobs in one of the following ways:
+ Through the MediaConvert console on the **Job settings** page, in the **Metadata** pane. 
+ Through the MediaConvert API in your job settings JSON payload. Include tags as shown in the following JSON snippet, in `userMetadata`. For more information, see the [Jobs](https://docs.aws.amazon.com/mediaconvert/latest/apireference/jobs.html) endpoint section of the *MediaConvert API Reference*.

  ```
  {
  	"name": "Job Template Test with Resource Tags",
  	"description": "Job Template Test",
  	"userMetadata":{
  		"Company": "Banana",
  		"Stage": "Production"		
  	},
  	"settings":{
  ```

 

## AWS Elemental MediaConvert job tag restrictions
Job tag restrictions

The following basic restrictions apply to tags on jobs:
+ Maximum number of tags per job – 10.
+ Maximum **Key** length – 128 Unicode characters.
+ Maximum **Value** length – 256 Unicode characters.
+ Valid values for **Key** and **Value** – Uppercase and lowercase Unicode letters in any language, numbers, space, and the following characters: \$1 . : / = \$1 - and @.
+ Tag keys and values are case sensitive.
+ Don't use the `aws:` prefix for either keys or values. It's reserved for AWS use.