Using roles with Amazon Chime SDK media pipelines - Amazon Chime

You must be an Amazon Chime system administrator to complete the steps in this guide. If you need help with the Amazon Chime desktop client, web app, or mobile app, see Getting support in the Amazon Chime User Guide.

Using roles with Amazon Chime SDK media pipelines

The information in the following sections explains how to create and manage a service-linked role for Amazon Chime SDK Media Pipelines.

Service-linked role permissions for Amazon Chime SDK media pipelines

Amazon Chime uses the service-linked role named AWSServiceRoleForAmazonChimeSDKMediaPipelines – Allows Amazon Chime SDK media pipelines to access Amazon Chime SDK meetings on your behalf.

The AWSServiceRoleForAmazonChimeSDKMediaPipelines service-linked role trusts the following services to assume the role:

  • mediapipelines.chime.amazonaws.com

The role allows Amazon Chime to complete the following actions on the specified resources:

  • Action: chime:CreateAttendee on all AWS resources

  • Action: chime:DeleteAttendee on all AWS resources

  • Action: chime:GetMeeting on all AWS resources

You must configure permissions to allow an IAM entity (such as a user, group, or role) to create, edit, or delete a service-linked role. For more information, see Service-Linked Role Permissions in the IAM User Guide.

Creating a service-linked role for Amazon Chime SDK media pipelines

You use the IAM console to create a service-linked role with the Amazon Chime SDK Media Pipelines* use case.

Note

You must have IAM administrative permissions to complete these steps. If you don't, contact a system administrator.

To create the role
  1. Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.

  2. In the navigation pane of the IAM console, choose Roles, then choose Create role.

  3. Choose the AWS Service role type, then choose Chime, then choose Chime SDK Media Pipelines.

  4. Choose Next.

  5. Choose Next.

  6. Edit the description as needed, then choose Create role.

You can also use the AWS CLI or the AWS API to create a service-linked role named mediapipelines.chime.amazonaws.com.

In the AWS CLI, run this command: aws iam create-service-linked-role --aws-service-name mediapipelines.chime.amazonaws.com.

For more information, see Creating a Service-Linked Role in the IAM User Guide. If you delete this service-linked role, you can use this same process to create the role again.

Editing a service-linked role for Amazon Chime SDK media pipelines

Amazon Chime does not allow you to edit the AWSServiceRoleForAmazonChimeSDKMediaPipelines service-linked role. After you create a service-linked role, you cannot change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see Editing a Service-Linked Role in the IAM User Guide.

Deleting a service-linked role for Amazon Chime SDK media pipelines

If you no longer need to use a feature or service that requires a service-linked role, we recommend that you delete that role. That way you don’t have an unused entity that is not actively monitored or maintained.

To manually delete the service-linked role using IAM

Use the IAM console, the AWS CLI, or the AWS API to delete the AWSServiceRoleForAmazonChimeSDKMediaPipelines service-linked role. For more information, see Deleting a Service-Linked Role in the IAM User Guide.

Supported Regions for Amazon Chime SDK media pipelines service-linked roles

Amazon Chime SDK supports using service-linked roles in all of the AWS Regions where the service is available. For more information, see Amazon Chime endpoints and quotas.