Amazon Transcribe identity-based policy examples - Amazon Transcribe

Amazon Transcribe identity-based policy examples

By default, IAM users and roles don't have permission to create or modify Amazon Transcribe resources. They also can't perform tasks using the AWS Management Console, AWS CLI, or AWS API. An IAM administrator must create IAM policies that grant users and roles permission to perform specific API operations on the resources that they need. The administrator must then attach those policies to the IAM users or groups that require those permissions.

To learn how to create an IAM identity-based policy using these example JSON policy documents, see Creating policies on the JSON tab in the IAM User Guide.

Policy best practices

Identity-based policies are very powerful. They determine whether someone can create, access, or delete Amazon Transcribe resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations:

  • Get started using AWS managed policies – To start using Amazon Transcribe quickly, use AWS managed policies to give your employees the permissions they need. These policies are already available in your account and are maintained and updated by AWS. For more information, see Get started using permissions with AWS managed policies in the IAM User Guide.

  • Grant least privilege – When you create custom policies, grant only the permissions required to perform a task. Start with a minimum set of permissions and grant additional permissions as necessary. Doing so is more secure than starting with permissions that are too lenient and then trying to tighten them later. For more information, see Grant least privilege in the IAM User Guide.

  • Enable MFA for sensitive operations – For extra security, require IAM users to use multi-factor authentication (MFA) to access sensitive resources or API operations. For more information, see Using multi-factor authentication (MFA) in AWS in the IAM User Guide.

  • Use policy conditions for extra security – To the extent that it's practical, define the conditions under which your identity-based policies allow access to a resource. For example, you can write conditions to specify a range of allowable IP addresses that a request must come from. You can also write conditions to allow requests only within a specified date or time range, or to require the use of SSL or MFA. For more information, see IAM JSON policy elements: Condition in the IAM User Guide.

Using the Amazon Transcribe console

To access the Amazon Transcribe console, you must have a minimum set of permissions for the console. These permissions must allow you to list and view details about the Amazon Transcribe resources in your AWS account. If you create an identity-based policy that applies permissions that are more restrictive than the minimum required permissions, the console won't function as intended for entities (IAM users or roles) with that policy.

To ensure that those entities can use the Amazon Transcribe console, attach the following AWS managed policy to them.

{ "Version": "2012-10-17", "Statement": [ { "Action": [ "transcribe:*" ], "Resource": "*", "Effect": "Allow" } ] }

You don't need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that you're trying to perform.

For more information, see Adding Permissions to a User in the IAM User Guide:

AWS managed (predefined) policies for Amazon Transcribe

AWS addresses many common use cases by providing standalone IAM policies that are created and administered by AWS. These policies are called AWS managed policies. Managed policies make it easier for you to assign appropriate permissions to users, groups, and roles than if you had to write the policies yourself.. For more information, see AWS Managed Policies in the IAM User Guide.

The following AWS managed policies, which you can attach to users, roles, and groups in your account, are specific to Amazon Transcribe:

  • ReadOnly – Grants read-only access to Amazon Transcribe resources so that you can get and list transcription jobs and custom vocabularies.

  • FullAccess – Grants full access to create, read, update, delete, and run all Amazon Transcribe resources. It also allows access to Amazon Simple Storage Service (Amazon S3) buckets with transcribe in the bucket name.


You can review the managed permission policies by signing in to the IAM console and searching by policy name.

You can also create your own custom IAM policies to allow permissions for Amazon Transcribe API actions. You can attach these custom policies to the IAM users, roles, or groups that require those permissions.

Permissions required for IAM user roles

When you create an IAM user to call Amazon Transcribe, the identity must have permission to access the S3 bucket and the AWS Key Management Service (AWS KMS) key used to encrypt the contents of the bucket, if you provided one.

The user must have the following IAM policy for decrypt permissions on the KMS Amazon Resource Name (ARN.)

{ "Version": "2012-10-17", "Statement": [ { "Action": [ "kms:Decrypt" ], "Resource": "KMS key ARN", "Effect": "Allow" } ] }

The user's IAM policy must have Amazon S3 permissions to access the S3 bucket where audio files are stored and transcriptions are saved.

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "s3:GetObject" ], "Resource": "S3 bucket location" } ] }

Permissions required for Amazon S3 encryption keys

If you are using an AWS KMS key to encrypt an Amazon S3 bucket, include the following in the AWS KMS key policy. This gives Amazon Transcribe access to the contents of the bucket.

{ "Sid": "Allow-Transcribe", "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::account id:root", }, "Action": [ "kms:Decrypt" ], "Resource": "KMS key ARN" }

For more information about allowing access to customer master keys, see Allowing external AWS Accounts to access a CMK in the AWS KMS developer guide.

Allow users to view their own permissions

This example shows how you might create a policy that allows IAM users to view the inline and managed policies that are attached to their user identity. This policy includes permissions to complete this action on the console or programmatically using the AWS CLI or AWS API.

{ "Version": "2012-10-17", "Statement": [ { "Sid": "ViewOwnUserInfo", "Effect": "Allow", "Action": [ "iam:GetUserPolicy", "iam:ListGroupsForUser", "iam:ListAttachedUserPolicies", "iam:ListUserPolicies", "iam:GetUser" ], "Resource": ["arn:aws:iam::*:user/${aws:username}"] }, { "Sid": "NavigateInConsole", "Effect": "Allow", "Action": [ "iam:GetGroupPolicy", "iam:GetPolicyVersion", "iam:GetPolicy", "iam:ListAttachedGroupPolicies", "iam:ListGroupPolicies", "iam:ListPolicyVersions", "iam:ListPolicies", "iam:ListUsers" ], "Resource": "*" } ] }