Troubleshooting AWS Elemental MediaTailor identity and access

Use the following information to help you diagnose and fix common issues that you might encounter when working with MediaTailor and IAM.

I am not authorized to perform an action in MediaTailor

If you receive an error that you're not authorized to perform an action, your policies must be updated to allow you to perform the action.

The following example error occurs when the mateojackson IAM user tries to use the console to view details about a fictional my-example-widget resource but doesn't have the fictional mediatailor:GetWidget permissions.

User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: mediatailor:GetWidget on resource: my-example-widget

In this case, the policy for the mateojackson user must be updated to allow access to the my-example-widget resource by using the mediatailor:GetWidget action.

If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials.

I am not authorized to perform iam:PassRole

If you receive an error that you're not authorized to perform the iam:PassRole action, your policies must be updated to allow you to pass a role to MediaTailor.

Some AWS services allow you to pass an existing role to that service instead of creating a new service role or service-linked role. To do this, you must have permissions to pass the role to the service.

The following example error occurs when an IAM user named marymajor tries to use the console to perform an action in MediaTailor. However, the action requires the service to have permissions that are granted by a service role. Mary does not have permissions to pass the role to the service.

User: arn:aws:iam::123456789012:user/marymajor is not authorized to perform: iam:PassRole

In this case, Mary's policies must be updated to allow her to perform the iam:PassRole action.

If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials.

I want to allow people outside of my AWS account to access my MediaTailor resources

You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources.

To learn more, consult the following:

• To learn whether MediaTailor supports these features, see How AWS Elemental MediaTailor works with IAM.

• To learn how to provide access to your resources across AWS accounts that you own, see Providing access to an IAM user in another AWS account that you own in the IAM User Guide.

• To learn how to provide access to your resources to third-party AWS accounts, see Providing access to AWS accounts owned by third parties in the IAM User Guide.

• To learn how to provide access through identity federation, see Providing access to externally authenticated users (identity federation) in the IAM User Guide.

• To learn the difference between using roles and resource-based policies for cross-account access, see Cross account resource access in IAM in the IAM User Guide.

MediaTailor cannot access my Amazon S3 bucket

If MediaTailor returns errors when trying to access content from your Amazon S3 bucket, check the following common causes:

Amazon S3 permissions issues

Error symptoms:

• 502 BadGatewayException with Amazon S3 related messages

• 403 Forbidden errors in MediaTailor logs

• Content fails to load from Amazon S3 origin

Resolution:

1. Verify your MediaTailor service role has the required Amazon S3 permissions:

   JSON

   {
       "Version":"2012-10-17",		 	 	 
       "Statement": [
           {
               "Effect": "Allow",
               "Action": [
                   "s3:GetObject",
                   "s3:GetObjectVersion"
               ],
               "Resource": "arn:aws:s3:::your-vod-bucket/*"
           },
           {
               "Effect": "Allow", 
               "Action": [
                   "s3:ListBucket"
               ],
               "Resource": "arn:aws:s3:::your-vod-bucket"
           }
       ]
   }
   

2. Check your Amazon S3 bucket policy allows MediaTailor access:

   JSON

   {
       "Version":"2012-10-17",		 	 	 
       "Statement": [
           {
               "Effect": "Allow",
               "Principal": {
                   "AWS": "arn:aws:iam::111122223333:role/MediaTailorServiceRole"
               },
               "Action": [
                   "s3:GetObject",
                   "s3:GetObjectVersion"
               ],
               "Resource": "arn:aws:s3:::your-vod-bucket/*"
           }
       ]
   }
   

HTTPS access issues

Error symptoms:

• SSL/TLS handshake failures

• 502 Bad Gateway when accessing HTTPS Amazon S3 URLs

Resolution:

1. Ensure your Amazon S3 bucket policy requires HTTPS:

   JSON

   {
       "Version":"2012-10-17",		 	 	 
       "Statement": [
           {
               "Effect": "Deny",
               "Principal": "*",
               "Action": "s3:*",
               "Resource": [
                   "arn:aws:s3:::your-vod-bucket",
                   "arn:aws:s3:::your-vod-bucket/*"
               ],
               "Condition": {
                   "Bool": {
                       "aws:SecureTransport": "false"
                   }
               }
           }
       ]
   }
   

2. Verify MediaTailor configuration uses HTTPS URLs for Amazon S3 content.

Cross-account Amazon S3 access

Error symptoms:

• Access Denied errors when Amazon S3 bucket is in different account

• MediaTailor cannot assume cross-account roles

Resolution:

1. Update the Amazon S3 bucket policy in the content account to trust MediaTailor's service role

2. Add cross-account permissions to MediaTailor's service role

3. Ensure both accounts have proper trust relationships configured