Using service-linked roles for MediaConnect - AWS Elemental MediaConnect

Using service-linked roles for MediaConnect

AWS Elemental MediaConnect uses AWS Identity and Access Management (IAM) service-linked roles. A service-linked role is a unique type of IAM role that is linked directly to MediaConnect. Service-linked roles are predefined by MediaConnect and include all the permissions that the service requires to call other AWS services on your behalf.

A service-linked role makes setting up MediaConnect easier because you don’t have to manually add the necessary permissions. MediaConnect defines the permissions of its service-linked roles, and unless defined otherwise, only MediaConnect can assume its roles. The defined permissions include the trust policy and the permissions policy, and that permissions policy cannot be attached to any other IAM entity.

You can delete a service-linked role only after first deleting their related resources. This protects your MediaConnect resources because you can't inadvertently remove permission to access the resources.

For information about other services that support service-linked roles, see AWS Services That Work with IAM and look for the services that have Yes in the Service-linked roles column. Choose a Yes with a link to view the service-linked role documentation for that service.

Service-linked role permissions for MediaConnect

MediaConnect uses the service-linked role named AWSServiceRoleForMediaConnect – The default Service-Linked Role that enables access to AWS Services and Resources used or managed by MediaConnect..

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

  • MediaConnect

The role permissions policy named MediaConnectServiceRolePolicy allows MediaConnect to complete the following actions on the specified resources:

  • Action: ecs:CreateCluster, ecs:RegisterTaskDefinition, ecs:DescribeTaskDefinition, ecs:ListAttributes, ecs:UpdateContainerInstancesState, ecs:DeregisterContainerInstance on Resource arn:aws:ecs:*:*:*

  • Action: ecs:UpdateCluster, ecs:UpdateClusterSettings, ecs:DescribeClusters on Resourcearn:aws:ecs:*:*:cluster/MediaConnect

  • Action: ecs:CreateService, ecs:UpdateService, ecs:RunTask, ecs:StartTask, ecs:StopTask, ecs:ExecuteCommand, ecs:PutAttributes, ecs:DeleteAttributes, ecs:DescribeServices, ecs:DescribeTasks, ecs:ListTasks on Resource arn:aws:ecs:*:*:* with the Condition of StringLike: {ecs:Cluster: arn:aws:ecs:*:*:cluster/MediaConnect}

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 MediaConnect

You don't need to manually create a service-linked role. When you create an associated MediaConnect resource in the AWS Management Console, the AWS CLI, or the AWS API, MediaConnect creates the service-linked role for you.

Important

This service-linked role can appear in your account if you completed an action in another service that uses the features supported by this role. Also, if you were using the MediaConnect service before January 1, 2023, when it began supporting service-linked roles, then MediaConnect created the AWSServiceRoleForMediaConnect role in your account. To learn more, see A new role appeared in my IAM account.

If you delete this service-linked role, and then need to create it again, you can use the same process to recreate the role in your account. When you create an associated MediaConnect resource, MediaConnect creates the service-linked role for you again.

You can also use the IAM console to create a service-linked role with the MediaConnect use case. In the AWS CLI or the AWS API, create a service-linked role with the MediaConnect service name. 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 MediaConnect

MediaConnect does not allow you to edit the AWSServiceRoleForMediaConnect 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 MediaConnect

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. However, you must clean up the resources for your service-linked role before you can manually delete it.

Note

If the MediaConnect service is using the role when you try to delete the resources, then the deletion might fail. If that happens, wait for a few minutes and try the operation again.

To delete MediaConnect resources used by the AWSServiceRoleForMediaConnect
  1. Delete all Bridges in all Gateways.

  2. De-register all Instances in all Gateways.

  3. Delete all Gateways.

To manually delete the service-linked role using IAM

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

Supported regions for MediaConnect service-linked roles

MediaConnect supports using service-linked roles in all of the regions where the service is available. For more information, see MediaConnect regions and endpoints.