Using Service-Linked Roles for MediaPackage

AWS Elemental MediaPackage uses IAM service-linked roles. A service-linked role is a unique type of IAM role that's linked directly to MediaPackage. Service-linked roles are predefined by MediaPackage and include all the permissions that the service requires to call other AWS services on your behalf.

A service-linked role makes setting up MediaPackage easier because you don’t have to manually add the necessary permissions. MediaPackage defines the permissions of its service-linked roles, and unless defined otherwise, only MediaPackage 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 MediaPackage 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 Role column. Choose a Yes with a link to view the service-linked role documentation for that service.

Service-Linked Role Permissions for MediaPackage

MediaPackage uses the service-linked role named AWSServiceRoleForMediaPackage – MediaPackage uses this service-linked role to invoke CloudWatch to create and manage log groups, log streams, and log events.

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

The role permissions policy allows MediaPackage to complete the following actions on the specified 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 MediaPackage

You don't need to manually create a service-linked role. When you enable access logging in the AWS Management Console, the AWS CLI, or the AWS API, MediaPackage creates the service-linked role for you.

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 enable access logging, MediaPackage creates the service-linked role for you again.

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

MediaPackage does not allow you to edit the AWSServiceRoleForMediaPackage 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 MediaPackage

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's not actively monitored or maintained. However, you must clean up the resources for your service-linked role before you can manually delete it.

Supported Regions for MediaPackage Service-Linked Roles

MediaPackage supports using service-linked roles in all of the regions where the service is available. For more information, see AWS Regions and Endpoints.