# Setting up AWS Elemental MediaConnect Setting up Before you start using AWS Elemental MediaConnect, you must sign up for AWS (if you don’t already have an AWS account) and create IAM users and roles to allow access to MediaConnect. This includes creating an IAM role for yourself. If you want to use encryption to protect your content, you also must store your encryption keys in AWS Secrets Manager, and then give MediaConnect permission to obtain the keys from your Secrets Manager account. This section guides you through the steps required to configure users and roles to access AWS Elemental MediaConnect. For background and additional information about identity and access management for MediaConnect, see [Identity and access management for AWS Elemental MediaConnect](security-iam.md). **Topics** + [ # Create non-admin roles ](setting-up-create-nonadmin-roles.md) + [ # (Optional) Set up encryption ](setting-up-encryption.md) # Create non-admin roles Users in the Administrators group for an account have access to all AWS services and resources in that account. Granting direct access to all AWS resources goes against the best practice of applying the least privileged permissions to a user. This section describes how you can create roles with permissions that are limited to AWS Elemental MediaConnect. This section also describes how your users can assume that role to grant secure and temporary credentials. **Topics** + [ ## Step 1: Create a non-admin policy ](#setting-up-create-nonadmin-IAM-policies) + [ ## Step 2: Create non-admin roles ](#setting-up-create-nonadmin-roles-create-role) + [ ## Step 3: Assume the role ](#setting-up-create-nonadmin-roles-assume-role) ## Step 1: Create a non-admin policy Create two policies for AWS Elemental MediaConnect: one to provide read/write access and one to provide read-only access. Perform these steps one time only for each policy. Later, you will attach these policies to roles. Those roles can then be temporarily assumed by users to grant access to MediaConnect. **To create policies** 1. Use your AWS account ID or account alias, and the credentials for your admin user, to sign in to the [IAM console](https://console.aws.amazon.com/iam). 1. In the navigation pane of the console, choose **Policies**. 1. On the **Policies** page, create a policy named `MediaConnectAllAccess` that allows all actions on all resources in AWS Elemental MediaConnect: 1. Choose **Create policy**. 1. Choose the **JSON** tab and paste the following policy: ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Action": [ "mediaconnect:*" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "ec2:DescribeAvailabilityZones" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "cloudwatch:GetMetricData" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "iam:PassRole" ], "Effect": "Allow", "Resource": "*", "Condition": { "StringLike": { "iam:PassedToService": "mediaconnect.amazonaws.com" } } } ] } ``` ------ This policy allows all actions on all resources in AWS Elemental MediaConnect. 1. Choose **Next: Tags**. 1. Choose **Next: Review**. 1. On the **Review and create** page, for ** Policy name**, enter **MediaConnectAllAccess**, and then choose **Create policy**. 1. On the **Policies** page, create a read-only policy named `MediaConnectReadOnlyAccess` for AWS Elemental MediaConnect: 1. Choose **Create policy**. 1. Choose the **JSON** tab and paste the following policy: ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Action": [ "mediaconnect:List*", "mediaconnect:Describe*" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "ec2:DescribeAvailabilityZones" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "cloudwatch:GetMetricData" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "iam:PassRole" ], "Effect": "Allow", "Resource": "*", "Condition": { "StringLike": { "iam:PassedToService": "mediaconnect.amazonaws.com" } } } ] } ``` ------ 1. Choose **Next: Tags**. 1. Choose **Next: Review**. 1. On the **Review and create** page, for ** Policy name**, enter **MediaConnectReadOnlyAccess**, and then choose **Create policy**. ## Step 2: Create non-admin roles You can create a role for each policy and users can assume that role, rather than attaching individual policies to each user. Using the following procedure, create two roles: one for the **MediaConnectAllAccess** policy and one for the **MediaConnectReadOnlyAccess** policy. **To create roles** 1. In the navigation pane of the IAM console, choose **Roles**. 1. On the **Roles** page, create an administrator role using the `MediaConnectAllAccess` policy: 1. Choose **Create role**. 1. In the **Select trusted entity** section, select **AWS account**. 1. In the **An AWS account** section, select the account with the users that will be assuming this role. 1. If a third-party will be accessing this role, it is a best practice to select **Require external ID**. For more information about external IDs, visit: [Using an external ID for third-party access](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user_externalid.html) in the *IAM User Guide*. 1. It is a best practice to require multi-factor authentication (MFA). You can select the checkbox next to **Require MFA**. For more information about MFA, visit: [Multi-factor authentication (MFA)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa.html) in the *IAM User Guide*. 1. Choose **Next** to move to the **Add permissions** section. 1. In the **Permissions policy** section, choose the **MediaConnectAllAccess** policy that you created in the procedure in [Step 3a: Create a Policy](#setting-up-create-nonadmin-IAM-policies). 1. Verify that the correct policies are added to this group, and then choose **Next**. 1. In the **Name, review and create** section, name the role `MediaConnectAdmins`. (Optional) Add a description for the role. Select **Create role**. 1. On the **Roles** page, create an administrator role using the `MediaConnectReadOnlyAccess` policy: 1. Choose **Create role**. 1. In the **Select trusted entity** section, select **AWS account**. 1. In the **An AWS account** section, select the account with the users that will be assuming this role. 1. If a third-party will be accessing this role, it is a best practice to select **Require external ID**. For more information about external IDs, visit: [Using an external ID for third-party access](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user_externalid.html) in the *IAM User Guide*. 1. It is a best practice to require multi-factor authentication (MFA). You can select the checkbox next to **Require MFA**. For more information about MFA, visit: [Multi-factor authentication (MFA)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa.html) in the *IAM User Guide*. 1. Choose **Next** to move to the **Add permissions** section. 1. In the **Permissions policy** section, choose the **MediaConnectReadOnlyAccess** policy that you created in the procedure in [Step 3a: Create a Policy](#setting-up-create-nonadmin-IAM-policies). 1. Verify that the correct policies are added to this group, and then choose **Next**. 1. In the **Name, review and create** section, name the role `MediaConnectReaders`. (Optional) Add a description for the role. Select **Create role**. ## Step 3: Assume the role After creating a policy and attaching that policy to a role, your users will need to assume that role to be granted secure and temporary access to MediaConnect. View the following resources for learning about granting permissions for users to assume the role and how users can switch to the role from the console or AWS CLI. + Granting a user permissions to switch roles: [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_permissions-to-switch.html](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_permissions-to-switch.html) + Switching roles (console): [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-console.html](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-console.html) + Switching roles (AWS CLI): [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-cli.html](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-cli.html) # (Optional) Set up encryption You can protect your content from unauthorized use through encryption. If your source is encrypted, AWS Elemental MediaConnect can decrypt it. In addition, the service can encrypt outputs and entitlements. AWS Elemental MediaConnect offers two options for encrypting content: static key and Secure Packager and Encoder Key Exchange (SPEKE). The steps to set up encryption depend on the type of encryption that you choose. For more information, see the following: + [Setting up static key encryption using AWS Elemental MediaConnect](encryption-static-key-set-up.md) + [Setting up SPEKE encryption using AWS Elemental MediaConnect](encryption-speke-set-up.md)