Using service-linked roles for data streaming

The following sections explain how to manage the service-linked role for data streaming.

Service-linked role permissions

Amazon Chime SDK uses the service-linked role named AWSServiceRoleForChimeSDKMessaging. The role grants access to the AWS services and resources used or managed by Amazon Chime SDK, such as the Kinesis streams used for data streaming.

The AWSServiceRoleForChimeSDKMessaging service-linked role trusts the following services so that those services can assume the role:

The role permissions policy allows Amazon Chime SDK to complete the following actions on the specified resource:

The following example shows the policy.

{
    	"Version": "2012-10-17",
    	"Statement": [
    		{
    			"Effect": "Allow",
    			"Action": [
    				"kms:GenerateDataKey"
    			],
    			"Resource": "*",
    			"Condition": {
    				"StringLike": {
    					"kms:ViaService": [
    						"kinesis.*.amazonaws.com"
    					]
    				}
    			}
    		},
    		{
    			"Effect": "Allow",
    			"Action": [
    				"kinesis:PutRecord",
    				"kinesis:PutRecords",
    				"kinesis:DescribeStream"
    			],
    			"Resource": [
    				"arn:aws:kinesis:*:*:stream/chime-messaging-*"
    			]
    		}
    	]
    }

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

You don't need to manually create a service-linked role. When you use the PutMessagingStreamingConfigurations API to create a data streaming configuration, Amazon Chime SDK creates the service-linked role for you.

You can also use the IAM console to create a service-linked role with the Amazon Chime SDK use case. In the AWS CLI or the AWS API, create a service-linked role with the messaging.chime.amazonaws.com service name. For more information, see Creating a service-linked role in the IAM user Guide. If you delete this role, you can repeat this process to create it again.

Editing a service-linked role

After you create a service-linked role, you can only edit its description, and you do that using IAM. For more information, see Editing a service-linked role in the IAM user Guide.

Deleting the resources used by a service-linked role

Before you can use IAM to delete a service-linked role, you must first delete any resources used by the role.

To delete resources used by the AmazonChimeServiceChatStreamingAccess role

Run the following CLI command to turn off data streaming for the app instance:

This action deletes all streaming configurations for your app instance.

Deleting a service-linked role

When you no longer need a feature or service that requires a service-linked role, it's a best practice to delete that role. Otherwise, you have an unused entity that is not actively monitored or maintained. However, you must delete the resources used by your service-linked role before you can manually delete the role.

You can use the IAM console, AWS CLI, or the AWS API to delete the AmazonChimeServiceRoleForChimeSDKMessaging service-linked role. For more information, see Deleting a service-linked role in the IAM user Guide.